Quiz — 6 questions
- The dispatcher scheduled action ships switched off. What is the argument for that default? → Waiting is recoverable and transmitting is not — a queued document is still generated, validated and intact, while a document fired at an unconfigured or wrong-environment endpoint is immutable, SHA-256 stamped, and has also spent its retry attempts
- Name the three scheduled actions and where you enable them. → E-Invoice: dispatch outbox, UAE E-Invoice: Poll ASP/FTA status and UAE E-Invoice: Fetch inbound documents, under Settings → Technical → Scheduled Actions, by a manager
- With a backoff base of 15 minutes, a ceiling of 4 hours and a maximum of 6 attempts, when does the last attempt run and what happens then? → At 16:45, 7 hours 45 minutes after a 09:00 failure; the dispatcher stops retrying and records why on the document
- Why are documents handed to the ASP without a result counted in their own column? → Because a percentage that absorbed them would climb during an ASP outage — from 98% to 99% in the worked month — while the honest reported figure fell from 96% to 65%
- A batch of invoices fails. How do you tell a transport failure from a rejection? → Transport: everything queued in that window is waiting and ageing together, no rejection reasons are arriving, and the reported column is flat. Rejection: a subset lands in Rejected / Failed, each with a named cause, and the reasons panel counts up
- What happens to an inbound supplier e-invoice, and who may see the ASP credentials? → It becomes a draft vendor bill and is never auto-posted, so you review and post it; the API key, secret, client id and webhook secret are visible to the Manager group only