Scheduling
A schedule runs a flow as a hosted run in your region, even when your browser is closed. A project can have several schedules.
Before you start
- You must be signed in, with Editor access or higher. Guests see "You can view schedules. Sign in with an account that can edit this project to make changes." People who only hold a share link can't schedule.
- On a team project, you must be a team member with Editor access or higher.
- The project needs a synced version. Otherwise you see "This project has no synced versions. Save and sync it before scheduling."
- Inputs must be Cloud files, URLs or connectors. A file on your computer is refused: "upload local inputs to Cloud before scheduling".
- Output blocks must save somewhere. A download or local file is refused: "choose a saved output destination before scheduling".
Create a schedule
- Open the dialog in one of these ways: Schedule in the Strata toolbar, Schedule in the details panel after selecting a project in Cloud, or Schedule this flow… in the settings menu under Automation.
- If the project already has a schedule, select Create schedule. If it has none and you can edit it, the form opens directly.
- Choose how often in Repeat. The options are below.
- Set Run date and time or Start date and time, then Time zone. The time zone starts as your browser's.
- To stop automatically, select End schedule and set End date and time. This isn't offered for Once.
- Check the summary box. Upcoming runs lists the next run times.
- Select Create schedule at the bottom.
You should see the schedule in the list with "Enabled" and its next run in your time zone.
Clear Schedule enabled to save it paused. It won't run until you select Resume.
Repeat options
| Repeat | What you set |
|---|---|
| Once | One run at Run date and time. |
| Every… | Run every (hours) and Minutes. The shortest interval is one minute. |
| Daily | Every day, such as a nightly run. Select Run only on weekdays (Monday–Friday) to skip weekends. |
| Weekly | Select the days to run. |
| Monthly | Monthly timing: Day of month with a Day, or On a weekday occurrence with Week of month and Weekday. Months without that date are skipped. |
| Custom | Select Days of the month and Months of the year. |
Choose which version runs
Open Advanced to set Schedule name (optional), Comments (optional) and Version:
- Latest synced version on a Branch runs whatever has synced to that branch when the run starts. That includes autosaved edits you have not named with Save.
- Freeze at a specific version pins the schedule to one saved version. Later edits don't affect it.
Pinning fixes the flow, not the data. Connected data is read when each run starts. Every run records the version it used.
If other people can edit a personal project, you must pin when the schedule is enabled. A paused schedule on the latest version can be saved, but enabling it or selecting Resume gives "Others can edit this project. Pick a fixed version so your usage only runs versions you chose."
Pause, resume and manage
Select All schedules in the Cloud toolbar to see schedules across your projects, then select one to open it. You can't create a schedule from that list.
- Edit changes the settings. Pause stops future runs and keeps the schedule. Resume starts them again.
- Run now starts a run straight away and leaves the regular timing unchanged.
- Delete then Confirm delete removes the schedule. Its run history is kept.
Who can change a schedule
A schedule runs as one person, shown as "Runs as". Their access is checked at every run.
- Personal project: only the creator can change or run it, because it spends the creator's usage. Others see "This schedule uses its creator's usage, so only they can change or run it."
- Team project: any team member with Editor access or higher can change or run it, and it spends the team's usage. The dialog warns "Saving or resuming makes this schedule run as you."
If the person it runs as loses access, or a file it needs can't be reached, the run fails and the schedule pauses. The dialog shows "Paused. Last run:" and the error. Other failed runs leave the schedule running.
Timing rules
- The 60-second rule. A run must start within 60 seconds of its time. If the service was unavailable for longer, that run is recorded as
skippedand is not made up later. - One at a time. If the previous run of the same schedule is still going, the new one is recorded as
skipped. - 5-minute maximum. A hosted run is stopped after 5 minutes and recorded as
killed. It is still charged. - Daylight saving. A time that happens twice runs once. A time that doesn't exist runs at the first valid time after it.
Next-run times in the list use your browser's time zone. Upcoming runs uses the schedule's time zone.
When a run fails
A run with no usage available is recorded as skipped and the schedule keeps going. Add usage to fix future runs.
What it costs
There's no separate scheduling fee. Each run spends usage like any hosted run, including failed and timed-out runs. See Pricing.
Share your work. Keep it in Cloud.
Store, schedule and share projects in one place.