> For the complete documentation index, see [llms.txt](https://docs.tpi.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tpi.dev/guide/system-information/recurring-tasks.md).
# Recurring Tasks
**Path: System Information > Recurring Tasks**
Recurring tasks is used to set periodic schedule tasks, such as: expiry date inspection of API keys and credentials. These schedules are usually set automatically by the system and the period, or they can be changed manually.
Recurring tasks is used to schedule tasks, as instructed in the following sections.
### Create Recurring Tasks
Most recurring tasks are scheduled automatically by the system, but schedules can also be created manually.
1. Click **Create** to access the creation page.
2. Fill in the data or make selections as instructed below. The fields marked with “\*” are required.
* **Task Name**\***:** Name that can identify the task.
* **Remark:** Remarks of the task.
* **Repeating Time**\***:** Frequency to execute the task, set to **Everyday** by default.
* **Start time** and **End time:** Define the start and end times for the recurring task.
\
If the start time is left blank, the schedule starts immediately. If the end time is left blank, the schedule runs indefinitely.
* **Add (schedule):** Add new task item here.
* **Order**\*: Order of scheduled tasks.
* **Type**\*: Type of the scheduled task.
* **Task**: Item of the scheduled task. The **Type**\* field must be set before proceeding with the selection in this field.
* **Parameters**: Parameters.
* **Identify Data**: Identifiable information.
* : Click to delete the schedule.
3. Click **Create** to save and exit.
### Search Recurring Tasks
Enter keywords or schedule statuses to search for recurring tasks.
### View Recurring Tasks
Search for the recurring task to view details, and click on theicon to access the recurring task details page.
### Edit Recurring Tasks
1. Search for the recurring task to modify, and click the  icon to access the edit page.
2. Modify the desired fields, and click **Confirm** to save and exit.
### Manage Recurring Tasks
In this section, you can find instructions on how to enable, suspend, disable, or skip the recurring task once.
1. Search for the task first, click on the  icon (as ➊ below) to expand the drop-down menu (as ➋ below), and click **active**, **Pause**, **Pause Once**, or **Disable** to enable, suspend, disable, or skip the recurring task once.
2. For schedules with the status **start up**, actions such as **Pause**, **Pause Once** and **Disable** will appear in the menu.
3. For schedules with the status **pause**, actions such as **active**, **Pause Once** and **Disable** will appear in the menu.
### View History of Recurring Tasks
1. Search for the recurring task to view history, and click on the  icon (as ➊ below) to open the drop-down menu (as ➋ below).
2. Click **History** to access the recurring task history page.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.tpi.dev/guide/system-information/recurring-tasks.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
