# Scheduling an Axon in Turium

* [Setting Up a Schedule](#setting-up-a-schedule)

Batch data axons can be set to operate on a certain schedule and frequency, such as every 4 hours or weekly on Monday at 1:30 AM.

Once an axon has been designed and deployed, a schedule can be established for it.

{% hint style="info" %}
Note: The schedules are set according to the AEST or UTC timezone. 
{% endhint %}

***

### Setting Up a Schedule  <a href="#setting-up-a-schedule" id="setting-up-a-schedule"></a>

To set an axon to run on a schedule, carry out the following steps:

* Navigate to the Deploy Axon page, and click the Schedule button.
* Set up the schedule.
* Frequency
* Starting time (and date, if necessary)
* Maximum concurrent runs: The limit is 10. If the maximum number of runs is already in progress, the next scheduled run will be skipped.
* Compute profile (optional): If a profile is not designated for the schedule, the default profile will be used.
* After making your selections, click Save and Start Schedule to both save and start the schedule or Save Schedule to save the schedule without initiating it. To begin a saved schedule, click Schedule and then click Start Schedule.

Once a schedule has been created, you can change it, initiate it, or put it on hold. From the Deploy Axon page, once you Start a schedule, you can click the Unschedule button to pause the schedule.

Similarly, you can modify a schedule by clicking the Schedule button and altering the schedule parameters.

***


---

# 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.turium.ai/home/algoreus/turium-connector-documentation/turium-fabriq-overview/how-to-guides/axons-pipeline-user-guide/scheduling-an-axon-in-turium.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.