Skip to main content

Failures

The Failures view of Diagnostics answers one question: what failed, and is it still open? It reads the stores where failures are recorded — validation findings, lifecycle events of the error statuses, the per-file rows of the runtime processing log, the job runs — and shows them in one list with the same columns, newest first.

Open it from Diagnostics → Failures.


At a glance​

Diagnostics · Failures📅 Yesterday ▾KINDValidation 30PA rejection 2Send / import 6Processing 3Job 1All templates ▾CompanyUnresolved only🔍 Search in messages (all pages)…↻ RefreshWHENKINDSOURCETEMPLATECOMPANYSTATUSRULEMESSAGE07:12ValidationF2026-1203invoices000019905BR-CO-15Total with VAT ≠ total + VAT↗06:40Send / importF2026-1188invoices000019904—Send failed: HTTP 503↗05:02ProcessingR42565_XJDE0001_…credit_notes———Transform failed↗04:00JobNightly BIP————Connection refused↗42 failure(s)Kind chipscounts · untick to leave outUnresolved onlyon by defaultOne shape for allvalidation, PA, send, file, jobServer-side searchacross every page of the resultRow actioninvoice · log · scheduled jobs

The kinds of failure​

KindRead fromSource column shows
ValidationThe validation findings of the invoice (XSD, Schematron, house rules).Invoice number
PA rejectionLifecycle events in a status of the errorBusiness group — by default refused, disputed, suspended, partially approved, routing error.Invoice number
Send / importLifecycle events in a status of the errorTech group — by default rejected (213), send failed, validation failed, import failed.Invoice number
ProcessingThe per-file rows of the processing log that ended in error.File name
JobThe failed runs of a scheduled job.Job name

The status groups come from the status catalogue, so a status added to errorTech or errorBusiness appears here without further setting.


Columns​

ColumnDescription
WhenTime of the finding or event.
KindOne of the five kinds above.
SourceInvoice number, file name or job name.
TemplateThe document the failure belongs to.
CompanyCompany of the invoice (invoice-linked kinds).
StatusCurrent status of the invoice.
LevelSeverity of the finding or event.
RuleValidation rule identifier, when there is one.
MessageThe error message.
ResolvedShown when Unresolved only is off.
ActionsOpen the invoice window, the processing log narrowed to the file, or the Scheduled jobs page.

Filters​

  • Period — yesterday by default.
  • Kind — chips with their counts; untick a kind to leave it out.
  • Template and Company — narrow to one document or company; the company grants of the signed-in user always apply to the invoice-linked kinds.
  • Unresolved only — on by default. Hides the failures the invoice, file or job has since moved past: the invoice left the error statuses or moved on from the event's status, or a later successful run exists for the file or the job.
  • Search in messages (all pages) — the search runs on the server, across every page of the result, not only on the rows displayed.

The grid has the usual tools of the shared data table: sorting, column choice, paging and export.


Tips & best practices​

  • Read it every morning with Unresolved only on. What remains is what needs a person.
  • Turn Unresolved only off to audit a period. Resolved failures show how often a rule or a platform fault came back.
  • Follow the row action. The invoice window carries the fix (edit, fix buyer, resend, reprocess); the processing log shows why a file failed; the Scheduled jobs page shows the job's run history.