> For the complete documentation index, see [llms.txt](https://docs.hidencloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hidencloud.com/hidencloud-panel/how-to-create-a-task.md).

# How to create a task?

Setting up scheduled tasks is essential to automate processes and ensure specific actions are executed at the right time. With [HidenCloud](https://docs.hidencloud.com/hidencloud-panel/www.hidencloud.com), you can create and manage scheduled tasks directly from the panel to streamline your operations.

## <mark style="color:blue;">Creating Schedule Tasks</mark>

* **Access the** [**HidenCloud Panel**](https://dash.hidencloud.com/dashboard)\
  Log in to your account and select the project or server where you want to configure the task.
* **Navigate to the Scheduling Section**\
  In the left sidebar, go to \[*Management*] > \[*Schedules*].
* **Configure a New Task**
  * Click the \[*Create Task*] button and fill in the following fields:
    * **Task Name**: Specify a name to identify the action.
    * **Frequency**: Choose when and how often the task should run (e.g., hourly, daily, or on a custom schedule).
    * **Command or Action**: Define the command or action to execute, such as custom scripts, server restarts, or clearing temporary data.
    * **Notifications**: Enable notifications to receive alerts when the task completes or fails.

<figure><img src="https://871593382-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVpfZZVBPNE9yhbxEmlqY%2Fuploads%2F9IRcZIjBGIFVnWnknAUy%2Fimage.png?alt=media&amp;token=a5e368ea-44ca-4d8b-8b35-374b95d29fa3" alt=""><figcaption><p>Creation of an assigned schedule</p></figcaption></figure>

<figure><img src="https://871593382-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVpfZZVBPNE9yhbxEmlqY%2Fuploads%2FxhvB6gjIDwuOfl4S0PVG%2Fimage.png?alt=media&amp;token=c4bf92e7-9a58-4cb2-ad7f-cb704497ec97" alt=""><figcaption><p>Assignment of a created schedule</p></figcaption></figure>

***

## <mark style="color:blue;">Edit or Delete Scheduled Tasks</mark>

1. **Access the** [**HidenCloud Panel**](https://dash.hidencloud.com/dashboard)\
   Log in and select your project.
2. **Navigate to Scheduled Tasks**\
   Go to \[*Management*] > \[*Schedules*].
3. **Locate the Task**
   * To **edit**, click the \[*Edit*] button, make the necessary changes, and save.
   * To **delete**, click the red trash icon and confirm the action.

{% hint style="warning" %}
Be cautious when deleting a scheduled task, as some automated actions might stop running and impact your operations.
{% endhint %}

***

## <mark style="color:blue;">View Tasks History</mark>

HidenCloud logs each execution of scheduled tasks, allowing you to monitor their performance and troubleshoot issues if necessary.

1. **Access the Scheduled Tasks Section**\
   Go to \[*Management*] > \[*Schedules*].
2. **View Execution Logs**
   * The task list displays:
     * **Date and Time** of each execution.
     * **Status** (e.g., completed, failed).
     * **Error Details**, if applicable.

<figure><img src="https://871593382-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVpfZZVBPNE9yhbxEmlqY%2Fuploads%2FvqnVplDUw9olK7UJ0npX%2Fimage.png?alt=media&amp;token=a3bb26c3-23cf-447e-92ca-f891805ef527" alt=""><figcaption></figcaption></figure>


---

# 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.hidencloud.com/hidencloud-panel/how-to-create-a-task.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.
