> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/triggers-and-webhooks/trigger-run-history-and-troubleshooting.md).

# Trigger Run History and Troubleshooting

Trigger history helps identify whether a workflow failed to start or failed after receiving an event. Inspect the trigger and run separately.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2Fs8PzCopMjQ8q7WRps7dj%2FG054.mp4?alt=media&token=d10f8f3a-4b01-4fe9-b3ec-50cedde84f3a>" %}

## Before you begin

Access to the trigger configuration and project run history.

## Key concepts

| Term           | Definition                                                                                                                              |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Activation     | The state in which a configured trigger can start work. Saving or listing a trigger does not establish that it is active.               |
| Event payload  | The data delivered by an event source. Map its actual fields and types to the receiving workflow inputs.                                |
| Run            | One execution of a project. Use its run ID to retrieve that execution’s state, input, output, and errors.                               |
| Trace          | Details of the steps taken during a run. Use it to locate the first unexpected input, output, or error.                                 |
| Reconciliation | Checking the run or destination to determine whether an uncertain operation completed. Do this before retrying a write after a timeout. |

## Diagnose a trigger run

1. Check that the trigger is active for the intended release.

![Check the trigger status and linked project in Settings → Triggers.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/7iA5jFr58vss4Xt6TqD1/assets/g054-g054-01-inventory.png)

Check the trigger status and linked project in Settings → Triggers.

2. Find the event or scheduled time in history and open its run.
3. Inspect received inputs, the failing node, and any provider error before changing configuration.

You can locate the stage that prevented the expected result.

## Behavior and limitations

An inactive trigger, a missing event, and a failed run need different corrections. Replaying an event can repeat external writes. Check the destination before replaying, and preserve event and run IDs when requesting support.

## Related resources

[Manage configured triggers](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/manage-configured-triggers.md)

[Trigger Activation and Execution Context](https://docs.stackai.com/technical-reference/triggers-and-webhooks/trigger-activation-and-execution-context.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/technical-reference/triggers-and-webhooks/trigger-run-history-and-troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
