> 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/guides-and-quickstarts/using-tools-and-actions/manage-configured-triggers.md).

# Manage configured triggers

Configured triggers start workflows on a schedule or in response to an event. The trigger list helps you find which project each trigger belongs to and whether it is enabled.

{% 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 start

Have a configured trigger and permission to edit its workflow. To create one first, use [Triggers and scheduled and event runs](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/triggers-and-scheduled-and-event-runs.md). Identify the intended deployment before changing its schedule.

## Locate the trigger and workflow

Open Settings → Triggers and locate the configured trigger.

![Configured trigger and linked workflow](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/7iA5jFr58vss4Xt6TqD1/assets/g054-g054-01-inventory.png)

Check its status before assuming a schedule or listener is active.

Open the linked project and inspect its workflow and run history.

![Configured trigger and linked workflow](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/abV14eaMqcrQ0AjgGTuy/assets/g054-g054-02-project.png)

Confirm that the trigger points to the project you intend to maintain.

## Change the schedule

Open Scheduled Execution and review frequency, time, and time zone.

![Scheduled execution configuration fields](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/8SrcrPdlF3Q262SLa5kR/assets/g054-g054-03-schedule.png)

The displayed time zone determines how the scheduled time is interpreted.

Change the schedule fields as required and save the draft.

![Scheduled execution configuration fields](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/EgMCvD0oftFmsJCsIcuz/assets/g054-g054-04-change.png)

Editing a draft schedule is separate from activating a deployed trigger.

## Review the processing path

Run the workflow manually to inspect the processing path.

![Triggered workflow processing results](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/IBfcHmfddPF8xbUiyXVj/assets/g054-g054-05-run.png)

A manual run checks the graph but does not prove that an external trigger fired.

Expand Output and inspect the value passed through from the trigger node.

![Triggered workflow processing results](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/4BrOJ54JSvX65v8dT4Pl/assets/g054-g054-06-output.png)

Distinguish a manual result from a run identified as Scheduled in Analytics.

## Save and check registration

Review and save the final intended schedule.

![Trigger schedule and registration status](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/JAU8uYMNm69PmHGvXtLQ/assets/g054-g054-07-restore.png)

Confirm the time zone as well as the hour before using it for automatic execution.

Return to Settings → Triggers and check the registration status.

![Trigger schedule and registration status](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/cXsSPg9swo8GkhsAuUom/assets/g054-g054-08-status.png)

Publication and trigger activation must be reviewed separately from the draft's schedule fields.

## Important behavior

A manual run checks the workflow steps. Use a run identified as Scheduled in Analytics to inspect a scheduled execution.

Saving schedule fields in a draft does not activate the deployed trigger. Check publication and registration status separately.

## Continue

* [Triggers and scheduled and event runs](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/triggers-and-scheduled-and-event-runs.md)
* [Publish and unpublish a project](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/publish-and-unpublish-a-project.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/guides-and-quickstarts/using-tools-and-actions/manage-configured-triggers.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.
