Scheduled jobs

A scheduled job is work your app does on its own at set times, such as a summary every morning or a cleanup every night. You describe it in the chat and Kuika AI writes it. You then manage your jobs in the Scheduled jobs panel.

Create a job

Say what should happen and when. Include the time zone, because "9am" means different moments in different places. Kuika AI tells you the schedule and time zone it chose.

Send a summary of yesterday's orders every day at 9am Istanbul time

If your app has no jobs yet, the panel shows a day timeline and three suggestions based on your own tables: a daily cleanup, a weekly summary and a monthly export. You can also type your own job there and press Create job. It goes to the chat, which writes the job.

To change an existing job, ask in the chat. Kuika AI keeps the schedule and time zone as they are unless you ask for new timing, such as "run it at 8am instead".

How schedules are written

Behind the scenes a schedule is a standard cron expression plus a time zone. For example, 0 9 * * * means every day at 9:00, and 0 2 * * 1 means every Monday at 2:00. You do not have to write these. The panel shows each schedule in plain words, such as "Every day at 9:00".

If a job points at a time zone Kuika AI does not recognize, or its schedule cannot be read, the job is skipped and the panel shows a warning under Manifest warnings.

See what happened

Open More, then Scheduled jobs. Each job is a card with:

• A status badge: Running, Active, Off, Auto-disabled, Removed or Handler missing.
• Its schedule in plain words and the time of the next run.
• A strip showing the last few runs.

Open a job to see its Run history. Each run shows whether it succeeded, failed, timed out or was skipped, with the reason, and whether it ran on schedule or was started by hand. Times are shown in the job's time zone.

Run now and switch on or off

• Press Run now to start a job right away. The result appears in the run history.
• Use the switch on a card to turn a job on or off.
• A job that keeps failing is switched off automatically, and a banner explains it. Fix the job or its data, then switch it back on yourself.

Good to know

• A job never overlaps with itself. If the previous run is still going, the new one is skipped.
• Each job has a daily cap on runs. The card shows how many runs you have used today. Once it is reached, the job runs normally again the next day.
• An app can have a limited number of jobs. Kuika AI tells you if you go over.
• In the preview, the app runs in your browser tab. When the tab is in the background, jobs wait until you come back.
• A job you add in the preview runs in the Test environment only after you publish again. See Test and production.
• The Test environment goes to sleep when nobody uses it, and its jobs run only while it is awake. The panel tells you when this applies.
• Jobs need an app with its own backend.