Are you an LLM? You can read better optimized documentation at /troubleshooting/error-messages.md for this page in Markdown format
Error messages
Mincemeat errors usually include a short message and may include a reference value. Use the message to decide what to check, and use the reference when support needs to investigate.
How to read an error
| Part | What it tells you |
|---|---|
| Message | The user-visible reason the action did not finish. |
| Field error | The specific form field that needs a different value. |
| Ref: | A correlation ID that support can use to find the matching event. |
What to do first
- Read the message and check whether it names a field or missing requirement.
- Copy the correlation ID if the error includes Ref:.
- Retry only if the action is safe to repeat.
- If the same error continues, prepare a support request.
Safe retry examples
- Signing in after correcting a password typo.
- Entering the next authenticator code.
- Saving a form after fixing a validation message.
- Refreshing a read-only list or detail page.
Avoid repeated retries
Do not repeatedly retry actions that create, delete, publish, or rotate important data. Collect the message and correlation ID, then contact support.