> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getswan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring trigger runs

> Where to see what your triggers have done, run statuses, visibility rules, and common failure reasons.

## Where to look

Every trigger fire creates a run you can inspect. Runs show up alongside your other [executions and history](../workspace/executions-and-history), and each run links back to the trigger that started it, the company or contact involved (if any), and the messages and tool calls Swan made along the way. A single trigger's own run history lives on its page at **Triggers → \[trigger] → Logs** (`https://agent.getswan.com/triggers/{triggerId}/logs`) — the trigger's page also has an Activity card with a "View logs" shortcut into the [Desk](https://agent.getswan.com/desk) filtered to that trigger.

You can search past runs by keyword or by meaning — the search understands what you're describing even if you don't remember the exact wording used in the run, and it also covers past conversations, not just trigger runs. You can filter by company, status, and date range.

## Who sees what

* **Admins** see the runs of every trigger in the organization.
* **Everyone else** sees the runs of org-wide triggers (the ones without a single owner) plus the runs of their own personal triggers. You won't see another member's personal trigger runs unless you're an admin.

## Run status

Each run has a status: pending, in progress, completed, failed, cancelled, or awaiting approval (when a step needs your sign-off before Swan continues). A run that finishes but only partially completes its instructions is still marked completed — check the run's summary for what it actually got done versus what it couldn't.

## Common failure reasons

* **Out of credits** — your organization had no credits remaining when the event fired. The run doesn't start; the trigger stays enabled and picks back up once you have credits again. See [how triggers work](how-triggers-work#credits).
* **Trigger disabled** — the trigger was turned off between the event being created and the run starting.
* **Disconnected integration** — a tool the run needed (a CRM, sender, or connected app) lost its connection. Reconnect it from [connected apps](../integrations/built-in-integrations) or your [senders](../outreach/senders-and-connected-accounts) and the next event will run normally.

## Common questions

**Can I re-run a failed trigger execution manually?**
There's no button to replay a specific past run, but you can ask Swan directly in chat to do the same work, or trigger it again through its normal source (for example, resending a webhook payload).

**Does a run that fails still cost credits?**
If a run fails early — before actually starting its work, including when it's blocked for insufficient credits — the flat per-event fee isn't charged. A run that starts and then fails keeps the per-event fee plus whatever billable actions it completed before failing.

**Why can't I find an old trigger run in search?**
Search covers your organization's execution history, but very old runs may fall outside the default date range — widen the date filter if you're looking further back.

**How do I know which trigger caused a company to move stages or get a task created?**
Open the run itself — it's linked from the company's activity and from the task on the [Desk](https://agent.getswan.com/desk), and shows the trigger name and the reasoning Swan used.