Prove the task by hand first
Run the work manually three times before scheduling it. Write down the inputs, the steps, and what a correct output looks like. If the output differs each time, the task is not ready.
A daily task should produce the same shape every day, even when the content changes. Shape is what lets you review it in thirty seconds.
Choose the schedule, then the timezone
Daily is usually a cron expression at a fixed local time, or a fixed interval of 86400 seconds. Choose one and write down the timezone, because a schedule without a timezone is a guess.
Pick a time when the inputs are ready, not a time when you feel productive. A daily report that runs before the source system updates will look wrong every day.
Make failure visible
Every scheduled task needs a visible record: last run, result, and next run. A task that fails silently is worse than no automation, because it creates confidence without output.
Add a simple rule: if a run fails, the task leaves a marker in a place you actually open. For most teams that is the same workspace where the output lives.
Review the first ten runs
Watch the first ten runs at the time they happen. Most issues appear in the first week: a source that publishes late, a holiday, a duplicated input, a format change.
After that, review weekly rather than daily. The goal is not to watch the task forever; it is to know which failure modes are real and which ones you can ignore.
Where this breaks
Daily tasks break on timezone changes, on days when the source is empty, and when one run overlaps the next. Set a concurrency policy and a timeout, and decide what a missed run should do.
They also break when the task does too much. Split a daily task that produces three unrelated outputs into three tasks, so a failure in one does not hide the other two.
How to run it on Sigla
Create the task in the workspace where the work already happens, choose the agent or method, and set the schedule. Use run now before enabling it, then read the run history after the first scheduled execution.
For the mechanics, read how to schedule recurring AI tasks. To keep the workspace running on your machine, continue with AI workspace on desktop.
FAQ
What time should a daily task run?
After the inputs are ready and before the first person who needs the output starts work. Write the timezone down with the schedule.
What happens if a run fails?
It should leave a visible record and follow the retry policy you set. Check that the failure is visible before you trust the schedule.
Can it run more than once a day?
Yes, use a shorter interval or a cron expression with more than one time. Watch the first runs for overlap before you increase the frequency.
What should a daily task not do?
It should not make irreversible changes without a review step. Keep approvals and sends manual until the task has a stable history.
Next step
Take one task you ran by hand this week, write the correct output shape, and schedule it for tomorrow morning.