# Logs & History

## Logs

On the Logs tab of a specific trigger, you can view all historical executions of that trigger and the object they acted on. Clicking on the relevant part of the row (i.e. issue number) brings you directly into the object, where you can see when in the Activity Log the trigger fired.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FJ1F20weLMR8n1VvWhtce%2FCleanShot%202025-06-03%20at%2021.28.09%402x.png?alt=media&#x26;token=75eda448-4883-4b21-9c46-c3422e2d02f1" alt=""><figcaption></figcaption></figure>

## History

By toggling the version history for a specific trigger, view all historical versions to understand when and why changes to your business workflows were made.

Use trigger history to:

1. Understand why changes in a workflow were made and who made them
2. Debug unexpected behavior by understanding the state of a trigger at a point in time
3. Rollback to a previous state to quickly iterate on your business process

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FLkxx9gcurZxX4vAr6Mx7%2FCleanShot%202025-06-03%20at%2021.29.15%402x.png?alt=media&#x26;token=bd5b7773-5b25-462c-97df-05b31dc95c69" alt="" width="563"><figcaption></figcaption></figure>

## Time Delay Queue

Triggers can have time delays as part of their control flow. With the time delay queue inspector you can see items that are part of the queue to be evaluated.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FFtapBGrgVzqkBYPdcErT%2FCleanShot%202025-06-03%20at%2021.22.50%402x.png?alt=media&#x26;token=48c4da6b-ff40-40f6-b555-83acec2388d7" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.usepylon.com/pylon-docs/platform/triggers/logs-and-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.