Los artículos de ayuda existen en alemán e inglés. Aquí los lees en inglés.
Calidad de datos y diagnóstico
What does a processing backlog mean?
A queue sits between reception and reporting. When it grows faster than it is worked off, a backlog forms: raw events are already there, journeys and conversions are not yet. If processing an event fails for good, the portal reports it as FAILED_JOBS for seven days; support can replay it.
Events have arrived but journeys are not appearing. Why?
The state of the queue appears under “Data status” in the “Processing” section, together with the delay between receipt and processing; if the backlog grows large, the health centre reports the finding PROCESSING_BACKLOG. A short backlog after a spike is normal; a permanently growing one is an operational problem.
- Short-lived: wait and check the view again later.
- Persistent: contact support and include the finding from the health centre.
- No events are lost in the meantime; they are processed once the queue catches up.
When processing fails
After several retries, processing gives up on an event. It is then missing from journeys and attribution until it is processed again. The portal reports such production events from the last seven days in three places with the same number: as a line on the overview, as the finding FAILED_JOBS in the health centre and as an open task under “Data status → Processing”.
- Write to support and quote the error code FAILED_JOBS; the support summary from the health centre is the easiest way.
- Support can replay the events affected once the cause is fixed. They then appear in journeys and attribution, and the notice disappears.
- If no new failure occurs, the notice disappears on its own after seven days.
Note
What intake rejects for an invalid format does not count here. Such data was never stored and cannot be replayed; it is listed as a data content finding under “Data status” (see “Why are my events rejected?”).
Revisado por última vez el 12 oct 2026
También se pregunta
- Queue backlog
- Processing is stuck
- Events present but no journeys
- FAILED_JOBS
- Events failed in processing
- Some events could not be processed
Artículos relacionados
- How long until data appears?
When do I see the first numbers after installing?
Individual events appear in the live test within seconds. Journeys and conversions are created during processing and usually appear within minutes; attribution shares are calculated afterwards.
- What does the setup health centre do?
How do I find out what is missing in my setup?
The health centre runs a diagnosis across your setup and reports every finding with cause, effect, error code and the steps to fix it, rather than just an error message.
- Why are my events rejected?
The collector does not accept events. How do I find the cause?
The collector response states a status per event and, on failure, the reason. Check that response first; “Data status” in the portal additionally summarises the reasons over the period.