Delivery Logs & Errors

Every delivery, successful or failed, is logged. This lets you diagnose problems quickly and trigger deliveries again when needed.

Delivery log: chronological list of all delivery attempts with status, timestamp, and error message.
Delivery log: chronological list of all delivery attempts with status, timestamp, and error message.

View Logs

Go to Data → Data deliveries, open the connection, and click Delivery Logs next to the meter you are interested in under Assigned metering points. You will see a chronological list of all delivery attempts for that meter with status, timestamp, and details. Logs are kept for 90 days.

The Delivery Logs tab of the connection lists every delivery of the connection in one place, and its Event column says what each one carried: measurement data or a consent event. A webhook's consent events are listed only there, because they cover every meter of your team, including meters not assigned to the connection.

Status Meanings

Status Meaning
Success Delivery was acknowledged by the target with a 2xx response
Failed Delivery has permanently failed (after all retries)
Retrying Delivery failed; further attempts are pending
Pending Delivery is in the queue and has not been processed yet

Error Diagnosis

For failed deliveries, the log shows the HTTP status code (for webhooks) or the error message (for MQTT). Common causes:

  • 4xx (e.g. 401, 403): Authentication failed. Check your token or signing secret.
  • 5xx: Server error on the recipient's side. Wait for availability or contact the system operator.
  • Timeout: The target is responding too slowly. Check the reachability and performance of the endpoint.
  • MQTT connection error: Broker unreachable or credentials incorrect.

Automatic Deactivation

When deliveries keep failing for an hour, you receive a notification and the connection stays on. After 72 hours without a successful delivery, the connection is automatically deactivated and you receive a second notification. A webhook whose endpoint answers 410 Gone is deactivated at once. The next successful delivery ends the failure period, so a brief outage of the recipient never switches a connection off. Consent events don't count here: a failed one never starts a failure period, and a delivered one never ends it. New readings will not be delivered for a deactivated connection until you reactivate it.

To reactivate a deactivated connection:

  1. Go to Data → Data deliveries.
  2. Open the deactivated connection.
  3. Fix the issue (e.g. update the URL or credentials).
  4. Switch Enabled back on and save the connection.

Resend Deliveries

Open the connection and click Resend next to the affected meter under Assigned metering points. Pick a start and an end date: every reading in that period is delivered again for that meter. This is useful when the recipient was temporarily unavailable.

To send one failed webhook delivery again, click Send again in its row of the delivery log. It carries exactly the same data and the same webhook-id, so your receiver can recognise a delivery it already processed.

Test vs. Live Deliveries

Deliveries triggered via the Send Test button are marked as test deliveries in the log. They count towards automatic deactivation just like live deliveries: a failed test delivery starts or continues the failure period, and a successful one ends it.