Troubleshooting
I got an error with a code
What that code is, why it is worth copying, and what to say when asking for help.
When something genuinely fails, the screen gives you a code in this shape: `E-260813-4F2A`. It is not decoration: it is the exact reference for what happened, with its time and context, stored on the platform side.
What to say when asking for help
- The code, exactly as shown.
- What you were trying to do, in one sentence.
- Whether it happened once or repeatedly.
That is enough. No screenshots or long explanations needed: the code already carries what the system was doing at that moment.
Before reporting it
- 1
Retry once: some failures are momentary.
- 2
Try another tab, to rule out the browser.
- 3
If it happens again, then report it, with the code.
Worth knowing
An error with a code means the platform knows something went wrong and has recorded it. That is better than a silent failure, even if it does not feel like it at the time.
Watch out
If the failure happens while paying or charging credits, do not repeat the operation several times before asking. Report it with the code.
›Is my work lost?
It depends where it failed. The code says.
›Can I look the code up myself?
The technical detail is for support. You provide the reference.
›How long is it kept?
Long enough to investigate it comfortably.
A real case
The situation
Saving a process throws an error with a code.
What you do
- Copies the code
- Retries and it fails again
- Emails support with the code and one sentence
What you get
It is resolved without the usual "which browser?, what time was it?" round.
The situation
The error notice is dismissed without noting the code.
What you do
- Copies the code before dismissing
What you get
Support locates the specific case in seconds.
The situation
A cropped screenshot is sent where the code is not visible.
What you do
- Includes the code in the message text
What you get
No second screenshot has to be requested.
The situation
The same code appears several times in a week.
What you do
- Reports the cases together with their times
What you get
The pattern is visible rather than treated as isolated incidents.
The situation
The error is reported days later.
What you do
- Writes the same day, giving the time
What you get
The logs still allow reconstructing what happened.
The situation
Two people report the same code separately.
What you do
- Checks whether a case is already open
What you get
Duplicated support work is avoided.
This article answers
- what does the error code mean
- i get an error when saving
- how do i report a bug
- error with reference e-