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 switcher at the top of the page:

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​

DiagnosticsIntegration errors by rule or by event, every failure in one list, the processing log and the server log.Integration errorsProcessing logFailuresServer log📅 Yesterday ▾By ruleBy eventDetailedUBL 38Integration 4RULEINVOICESDESCRIPTIONTEMPLATESTATEBR-CO-1524Invoice total with VAT = total without VAT + VATinvoicesOpenBR-FR-129Buyer SIREN is mandatoryinvoicesOpenBR-S-085VAT breakdown per ratecredit_notesOpenXSD4Element out of sequenceinvoicesResolvedFour views, one pageeach view granted on its ownBy rule firstthe morning readRule descriptionfrom the Schematron packsYesterday by defaultchange the period hereShared 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.
  • Yesterday by default. Every dated view starts on yesterday's activity; 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.