About logs
The five pipeline stages every message passes through, and what can go wrong at each one.
Every message the system handles is recorded, stage by stage. Understanding those stages is what makes the logs readable — an outcome on its own tells you a message failed, but the stage tells you where.
The five stages
A message passes through five stages in order. Each is recorded separately, and a failure at one means the later stages were never reached.
| Stage | Question it answers | Possible results |
|---|---|---|
| Grammar | Could the message be read? | Matched, Invalid format, Unknown code |
| Reporter | Is the sender recognised? | Found, Not registered |
| Event | Was it written to DHIS2? | Created, Failed |
| Reply | Did DHIS2 take the answer to the reporter? | Accepted by DHIS2, Rejected by DHIS2, Invalid number |
| Notifications | Did DHIS2 take the alerts to the recipients? | All accepted, Partly rejected, All rejected, None, Not reached |
Not reached is not a failure — it means an earlier stage stopped the message before this one could run.
Accepted by DHIS2 means DHIS2 agreed to send the message, not that a phone received it. What happened afterwards is tracked per message on the delivery page.
Outcomes
The overall outcome summarises the whole journey: Success, Unauthorized, Invalid message, Unknown code, Unregistered sender, Reply rejected, Event failed, or Error.
Outcomes point at different owners. An unregistered sender or unknown code is usually a configuration or registration matter. Event failed points at DHIS2. Reply rejected means the reporter was not answered: either DHIS2 refused the reply, which points at its SMS set-up or the SMS gateway, or the reporter's own number is unusable, which points at their record in DHIS2. Reading the outcome first, then the stage, is the quickest route to the right place.
Where to look
Logs explorer
Find and inspect individual messages, filter by any field, and follow live traffic.
Health overview
Volume, replies accepted, the gateway panel, and which codes are arriving.
Delivery and pipeline health
What became of every outgoing message, and which part of the pipeline is in trouble.
Use the overview to notice that something is wrong, and the explorer to find out what.