New Job

Steps to create a Job:

1.Start a New Job

Click on the green button with the "+" symbol.

2. Select Manual Job Creation

Choose "Create job manually" from the available options.

3. Click on "Nodes".

4.Add Control and Extraction Nodes

Select the control node and drag it to the right, along with the extraction nodes you need.

4. Link the nodes.

Connect the nodes by dragging from one to another, defining the flow of execution.

5. Save Your Job Structure

Click the green button to save the changes.

6. Click on "Panel".

7. Set a Job Name

Go to the "Panel" section and update the job name for easy identification.

8. Schedule Execution

Click on "Schedule Execution" to configure how often the job should run. Depending on the selected option, you'll be able to define specific scheduling parameters.

Scheduling Options

Once Only

Run the job only one time at a specific date and time.

Once per Day

Run the job once per day. Select the days of the week and the time it should run.

Once per Month

Run the job once per month. Choose the day of the month and the execution time.

More than Once per Day

Run the job multiple times per day. Select the days of the week and define how often it should repeat within a day.

Custom Cron

Use a standard cron schedule expression to define custom execution intervals. This method is ideal for users familiar with cron syntax who need precise control over the schedule.

9. Confirm the Scheduling

Once you’ve defined the execution schedule, click on "Schedule Job" to finalize and activate it. And that's it! The job with the scheduled execution has been successfully created.

Time zones in scheduled jobs

Whichever scheduling option you use (Once per Day, Custom Cron, etc.), the time you enter is saved exactly as you typed it — in wall-clock time — along with the time zone of the browser you were using at the moment you saved the schedule. Crestone does not convert that time to UTC.

info

The time zone is captured once, when the schedule is saved, and stays fixed for that schedule from then on — it does not update automatically if you later open Crestone from a different time zone.

This matters in two common situations:

• Teams spread across countries: if a colleague in a different time zone created or last edited a job's schedule, the "next execution" shown in Crestone is calculated using their browser's time zone at the moment they saved it — not yours. Before assuming a schedule is wrong, check who configured it and from where.
• Editing an existing schedule: if you open and re-save a schedule from a different time zone than the one it was originally created in, the new time zone (yours) is the one that gets stored, and the execution time may shift as a result. If you only need to review a schedule without changing it, avoid re-saving it.

warning

A schedule created before Crestone started recording the browser's time zone falls back to UTC by default. If an older job's execution times look off by a fixed number of hours, this is the most likely cause — re-save its schedule to pick up the correct time zone.