Jobs

Use Jobs in Atoms Cloud to view and manage scheduled tasks for your project. Jobs run app logic on a schedule, such as cleaning up data, syncing inventory, preparing reports, or publishing scheduled content.

Create and update jobs in project chat, then use the Jobs panel to check their schedules, review run history, and enable or disable future runs.

Open Jobs

1. Open your project and connect it to Atoms Cloud if needed.
2. Open the Cloud panel.
3. Select Jobs in the sidebar.

The list shows each job's name, status, schedule, and last run time. Use Refresh to load the latest information and the pagination controls to browse more jobs.

Create a scheduled job

1. Return to your project chat.
2. Describe what the job should do and when it should run. Include the data it should use and the result you expect.
3. Review the implementation and confirm the intended schedule, including the time zone for any fixed time.
4. After the job is created, return to Cloud → Jobs and click Refresh.
5. Open the job to check its schedule and status. After it runs, review the run history and confirm the expected result in your app.

For example: “Create a scheduled job that checks inventory every 5 minutes and updates the product availability in my database.”

If the list says No jobs are scheduled yet, create a job in chat and refresh the panel. The Jobs panel focuses on viewing tasks and switching them on or off; creation and changes are handled through chat or the SQL editor.

Understand job and run statuses

A job's status controls whether it is scheduled to run:

• Active: the job is enabled and can run according to its schedule.
• Disabled: future scheduled runs are stopped. Previous run records remain available.

Each individual run has its own result:

• Running: the run is still in progress.
• Succeeded: the run completed successfully.
• Failed: the run ended with a failure.

An Active job can still have a failed run. Check run history to see what happened during each execution.

View run history

1. In Cloud → Jobs, select a job.
2. Review its schedule and Last run time.
3. Check the run history table for the run number, start time, end time, and status.
4. Use Refresh for the latest results, or browse earlier records with the pagination controls.

Runs appear with the most recent first. A job with no executions yet shows an empty history.

Disable or enable a job

1. Open the job's details.
2. Click Disable to stop future scheduled runs, or Enable to allow the job to run on its schedule again.
3. Check the updated status and the confirmation message.

Disabling a job does not cancel a run that is already in progress. That run continues to completion and is recorded with its actual result. Disabling also keeps the job's schedule, logic, and previous run history.

Change or delete a job

Use project chat to change a job's schedule or logic, or to delete it. Identify the job by name and describe the change clearly.

• Change a schedule: “Change the inventory sync job to run every 30 minutes.”
• Change its behavior: “Update the inventory sync job to process only products marked as active.”
• Remove a job: “Delete the inventory sync scheduled job.”

Advanced users can also create, modify, or delete jobs in the SQL editor. After a change, return to Jobs and refresh to verify the result. Use Disable if you only want to pause future runs.

Manage usage

Jobs that run often or take longer to complete can increase resource usage. Choose a schedule that matches your app's needs, keep each task focused, and disable jobs you no longer need to run. Review the usage information shown in the Cloud panel.

Troubleshooting

A new job does not appear

Check that you are viewing the correct project, confirm the job was created successfully in chat, and refresh the Jobs list.

A job has no run history

Check that the job is Active and review its schedule. If its first scheduled time has not arrived, there may be no run records yet. For a fixed-time schedule, confirm the intended time zone in chat.

A run failed

Identify the job name and failed run time in its history. Ask Atoms in project chat to investigate the job logic and any services or data it depends on. After applying a fix, review the result of a subsequent run.

A disabled job still shows a Running entry

The run may have started before the job was disabled. Disabling prevents future scheduled runs while allowing the current one to finish. Refresh the history to see its final result.