An export is only useful if the customer gets the file.

The worker can finish while the download fails. Braith connects those events so a successful job does not hide an unsuccessful customer task.

Connect with Pro · £59/month Try Free

Connect first. Pay only when you explicitly activate a paid plan.

Follow the report to its destination.

Export requested
Export completed
Download failed

Choose a boundary your application can actually observe: a valid file made available, an authorised download, or a confirmed client result. Do not call a button click proof of successful delivery.

See the failed result and who it affects.

Repeated supported failures can become one incident, with affected users and the events behind it. Open the incident to investigate the task rather than searching unrelated logs.

Braith incident showing three affected users and a failed download after an export reported completion.

An empty report can be correct.

Some filters legitimately produce no rows. Configure evidence that distinguishes this from a broken export. A missing download event alone remains unknown; a failed download response or invalid output can provide explicit failure evidence.

Troubleshoot a completed export with an empty file.

See what happens in your app.

Braith reviews sampled customer activity for likely problems, including flows you have not defined. Core outcome checks add context where you need it.

Connect with Pro · £59/month Try Free

Connect first. Pay only when you explicitly activate a paid plan.