---
id: KB-PR-006
url: https://app.codecontract.io/help/troubleshooting/something-failed-and-i-got-a-code
idioma: en
categoria: problemas
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-PR-001, KB-CD-002]
citadoPor: [KB-PR-009, KB-PR-010]
---

# I got an error with a code

_What that code is, why it is worth copying, and what to say when asking for help._

**Responde a:** what does the error code mean · i get an error when saving · how do i report a bug · error with reference e-

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.

**En corto**

- Copy it before closing the message. Without it, what happened has to be reconstructed.
- It contains none of your data: it can be emailed safely.
- With the code, support goes straight to the fault instead of asking you ten questions.

## 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.**

> [!NOTE]
> 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.

> [!WARNING]
> 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.

## Ejemplos

**Saving a process throws an error with a code.**

- Copies the code
- Retries and it fails again
- Emails support with the code and one sentence

→ It is resolved without the usual "which browser?, what time was it?" round.

**The error notice is dismissed without noting the code.**

- Copies the code before dismissing

→ Support locates the specific case in seconds.

**A cropped screenshot is sent where the code is not visible.**

- Includes the code in the message text

→ No second screenshot has to be requested.

**The same code appears several times in a week.**

- Reports the cases together with their times

→ The pattern is visible rather than treated as isolated incidents.

**The error is reported days later.**

- Writes the same day, giving the time

→ The logs still allow reconstructing what happened.

**Two people report the same code separately.**

- Checks whether a case is already open

→ Duplicated support work is avoided.