Describe the task once and say when it should run, in your own words. Before it starts, a test run shows every action it would take, and you decide which of them may run without asking. Every result lands in the schedule’s own conversation.
The Schedules page: what runs next, and each schedule with its timing and status. Example data.
How it works
Describe the task
Write what Stedia should do each time and when, for example “every weekday at 7:30”.
Test it and allow
A test run sends nothing and lists each action that would ask first, for you to allow.
Let it run
Each run writes into the schedule’s conversation, and anything you did not allow waits for you.
In detail
Timing in your own words
Describe the cadence in your own words, for example “last working day of the month at 9” or “every second Tuesday”. Stedia shows what it understood and the next three runs before anything changes. You can also set it by hand: daily, on weekdays, monthly by weekday or by date, or at a fixed interval of at least 5 minutes.
Tested before it goes live
Nothing runs on its own until the last setup step. “Start test run” carries out the task once, denies every action that would ask first and delivers nothing. To activate the schedule, you allow each action it found, one by one. If you change the task later, the schedule stops until you test it again.
With an assistant or without
Under “Run as” you pick an assistant, and the schedule follows its instructions and uses its tools. Without one, you switch on web search, image generation or knowledge bases for this schedule under “Options”. There you also pin the stationery its documents are printed on, and set how long a run waits for an approval, from 1 hour to 7 days.
Results in one conversation
Every run writes into the schedule’s conversation, so a run can build on what the last ones concluded and on replies you left there. Ask for a PDF or a Word file when you want to pass the result on. To give each run a fresh conversation, turn off “Runs build on each other” under Settings → Replies.
You see what happened
Each schedule shows a timeline with its past runs and the next ones. “Inspect run” shows step by step what a run did, and you approve open steps right there. Runs are kept for 180 days. The conversations they wrote to stay after that.
When something gets stuck
After 3 failed runs in a row, a schedule is marked “Failing” and shows up on the Activity tab. After 5, Stedia switches it off and emails its owner. A run that did not finish says why on its page, for example that a tool is no longer connected. “Run now” starts a real run at any time.
Hosted in the EU, AI in the EU if you choose. Built in Austria, GDPR compliant.