# Activity and evidence

> The durable record of every run, and how to re-run or retry from it.

**Activity** is the durable history of sync runs, image checks and S3 Batch
jobs. It answers the question a reviewer asks after a move: what exactly was
done, and what exactly was verified?

## What a run record holds

![Activity page listing completed and failed runs with route, payload, duration and run id](console:activity)

- Per-service counts: attempted, succeeded, skipped and failed.
- The run's logs.
- The outcome of each resource.
- For S3 Batch, a **waybill**: the evidence record of the job.

When an older record is missing a fact, it shows **"Not recorded"** instead
of a zero. A zero means zero.

## Re-run and Retry failed

From a run record you can:

- **Re-run** the same request.
- **Retry failed resources** only.

Both start from the recorded request, so a retry repeats what was reviewed.
Queued jobs re-check their bound configuration when they start.

## Audit log and log delivery

Admins also have an audit log with configurable scope, retention and row cap.
Audit and run logs can be delivered to an S3 bucket and prefix the admin names.

Source: https://douklar.app/docs/douklar/activity-and-evidence (Douklar docs, last checked 2026-10-17)