> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/builder/builder/schedules-and-frequency-based-triggers/frequency-based-triggers/editing-an-existing-trigger.md).

# Editing an Existing Trigger

To edit an existing trigger, go to the 'Schedules' section from the toolbar link in Builder:

![](https://3859925423-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MWYnDNwe3Cuo4zlGbs5%2F-MWpixQQ-XB_sHNapfgn%2F-MWpu6DMQSw7lD9RiURm%2Fimage.png?alt=media\&token=b9b6b0bb-8022-4c99-9fe8-591c292e5eaa)

Then select the 'Triggers' option from the drop-down to access the Triggers page.

![](https://3859925423-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWYnDNwe3Cuo4zlGbs5-887967055%2Fuploads%2Fe95wGXbBZgxCGqg3aDfI%2Fimage.png?alt=media\&token=2294b528-d944-4d5a-acf0-2f752fdb5d71)

Here you can see a list of all of your existing triggers.

You can create, edit, pause, start or delete triggers from this here. You will also be able to see the name of the trigger, the work items it is being used for, how often the trigger runs, the time zone the trigger is set to run in, when the trigger was first run, last run and when it is due to run next according to the time zone selected.

You are able to change the time zone set for a trigger, but note that this will not have an effect until after the currently calculated next run-date. After the next run-date, the run-time of the trigger will change to show in the time of the chosen time zone

Additionally, if the trigger is set to run through daylight saving time, the time shown will now take into account daylight saving time.


---

# 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.enate.net/enate-help/builder/builder/schedules-and-frequency-based-triggers/frequency-based-triggers/editing-an-existing-trigger.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.