Skip to main content

Diagnostics

Diagnostics is the single page for everything that went wrong and everything the server wrote down. It hosts four views, picked from a row of compact cards under the header, each saying what it shows (the full text on hover); only the views the role grants are shown, and the row is hidden when a single view is left:

ViewWhat it answersPage
Integration errorsWhich validation rules fail, on which invoices — by rule (the default) or by event.Integration errors
Processing logWhat each processing run did, file by file, step by step.Processing log
FailuresEvery failure in one list — validation, PA rejection, send and import, processing, job — unresolved by default.Failures
Server logThe tail of the server log file, with severity and module filters.Server log

Open it from the sidebar — Diagnostics, in the Navigation group.

At a glance​

DiagnosticsErrors, failures and logs of the instance.Integration errorsFindings by rule, by event or in detailProcessing logEvery run with its files and statusFailuresEvery unresolved failure in one listServer logBy severity and moduleBy ruleBy eventDetailed📅 1 – 31 Oct 2026 ▾RULEINVOICESDESCRIPTIONTEMPLATESTATEBR-CO-1524Invoice total with VAT = total without VAT + VATinvoicesOpenBR-FR-129Buyer SIREN is mandatoryinvoicesOpenBR-S-085VAT breakdown per ratecredit_notesOpenFour view cardsonly the granted viewsIntegration errorsopens by ruleHover a cardits full descriptionPerioddefault period of the viewShared data tablesort, columns, paging, export
  • One grant per view. Each view keeps the page grant it had before it joined Diagnostics: Integration errors, Processing log, Server log, plus Failures for the new view. A role sees only the views it is granted, and the sidebar shows Diagnostics as soon as one of them is granted. See Roles.
  • Links land on the right view. The cards of the Dashboard and the Tech dashboard open Diagnostics on the matching view, with the same filters.
  • One default period per view. Each dated view opens on the default period set for it (Diagnostics, Integration errors, Processing log), this month unless set; change the period from its bar.
  • Integration errors opens by rule. The by-rule grid is the first read of a morning; switch to the event list from the view itself.

Tips & best practices​

  • Start from Failures when the question is "what needs fixing": it gathers the four kinds of failure and hides those already resolved.
  • Drill into Integration errors when one validation rule dominates: the by-rule grid groups the invoices by rule and source.
  • Use the Processing log for a file, the Server log for the server — a failed run shows in the first, an exception or a connection problem in the second.