
Use case / Automation agents
Debug the chain, not the final error.
Automations fail in the middle, retry, and sometimes do the same thing twice. Follow the whole chain, including retries, queues and fallbacks, to see what really ran.
- Retries
- Lineage
- Side effects
- Tracked
- Fallbacks
- Visible
Execution chain
Debug the chain, not the final error.
Each trigger starts a trace, so you can find the run behind any outcome.
The compiled plan shows what the agent meant to do before anything happened.
A timeout is just one span. The retry lineage shows what it caused next.
Fallbacks are recorded with the step they replaced.
Idempotency checks show whether the same action ran twice or was stopped.
- 01ok
Trigger accepted
Webhook from the billing system.
- 02ok
Plan compiled
Eight steps, two external calls.
- 03retry
Tool timed out
Retried with the same payload.
- 04ok
Fallback executed
Queue picked up the same job.
- 05ok
Duplicate prevented
Idempotency key matched the first attempt.
What Tracify watches.
Retry lineage
Recorded on every run, so it can be searched, compared and alerted on.
Idempotency
Recorded on every run, so it can be searched, compared and alerted on.
Queue latency
Recorded on every run, so it can be searched, compared and alerted on.
Fallback outcome
Recorded on every run, so it can be searched, compared and alerted on.

The failure to catch
A retry that quietly performs the same action twice.
Follow multi-step automations through retries, queues, fallbacks, and external side effects.
Instrument it
Trace the chain, not just the end.
Wrap each step of the workflow and retries show up as their own spans, so a duplicated side effect is visible instead of silent.
$ npm install tracify-sdk
import { observe, traceAgent } from "tracify-sdk";
const chargeCard = observe(async function chargeCard(order: Order) {
return billing.charge(order.id, { idempotencyKey: order.id });
}, { type: "tool" });
export const runOrder = traceAgent(async (order: Order) => {
await chargeCard(order);
return fulfil(order);
}, { environment: "production" });