This record has no interpretation yet, so one attached to another record of the same string key is shown for reference. The value may have changed since.
String Interpretation
Analysis Summary
Success, failure, and privacy copy for saving Discord app settings, including values marked as secret.
Detailed Explanation
The interface says values marked as secret go directly into a locked vault, never appear in chat, and are not shown to the creation conversation.
Settings saved is the completion state, while Those didn’t save asks the user to check the values and retry.
The same group says saving starts a quick rebuild before changes land.
These are interface claims; this run does not independently verify the underlying vault implementation.
May appear immediately after saving regular or secret values in an app project's settings, including validation or storage failure.
What It Means
The interface treats secret fields as separate locked inputs; a successful save starts the path that applies changes, while a failure means the current values need checking and another attempt.
What To Do
Enter sensitive values only in fields marked as secret and do not paste them into the project chat.
After a save failure, verify the inputs and retry from the same settings surface.
Search Intent
A search to understand where secret app settings are entered, what Settings saved or a save failure means, or why saving starts a rebuild.
Related Phrases
Settings saved
Save settings
secret
locked vault
rebuild
try again
Evidence
The current Canary locale group contains locked-vault and no-chat copy, Save settings, Settings saved, check-and-retry failure text, and the rebuild notice together.