Schedule a recurring backup
DBA / team recipe: create a timer, attach it to a backup flow, and keep tagged snapshots coming while the agent is online.
Role: DBA or team · Screen: Company Setup → Timers, then flow edit · Time: about 10 minutes after a backup flow exists
This page is the clicks. For why automation matters, read Never Forget to Backup Again. There is no quemsi timer create CLI; timers live under Company Setup.
Before you start
- A backup flow already exists (created when you first took a snapshot). If not, Take a tagged snapshot from the Data timeline (Quick Backup Wizard if Data is empty).
- The agent that runs the flow stays ONLINE at the scheduled time. Timers fire on the agent, not in the cloud.
- Decide the tags every scheduled run should carry (for example
app=quemsianduse-case=nightly). Restore shows the latest version per tag combination, which is usually what you want for a nightly card.
Steps
Set default execution tags on the flow
Open the backup flow (Flows → the flow → edit). Under Default execution tags, add the tags scheduled runs should always apply. Save with Update Flow.
Timer ticks use these tags (plus system tags and timer=<timer name>). They also pre-fill Execution Tags when you Take Snapshot from the timeline.
Create a timer
Open Company Setup → Timers (/app/setup/timers). Click Add Timer (or Create Your First Timer if the list is empty).
On Add Timer fill:
- Name — URL-friendly (letters, numbers, hyphens, underscores), for example
daily-midnight. - Title — display name, for example “Daily midnight backup”.
- Schedule — pick a preset chip, or type a Quartz cron expression. Presets include every day at midnight, every Sunday at noon, every Monday at 6am, and month-start / month-end options. The field help links to a Quartz cron generator.
Click Save.
You can also create a timer from the flow’s Timer card: the + control next to Select a timer opens the same Add Timer page and returns you to the flow.
Attach the timer to the backup flow
On the flow edit page, left column, the Timer card:
- Check Run regularly.
- Choose the timer under Select a timer.
- Save the flow (Update Flow).
The agent reloads the flow. Flow cards on the Flows list show the attached timer.
Verify the first run
Wait for the schedule, or open the data item and click Take Snapshot now to prove tags and storage. After a timer tick, the new version on the timeline should include your default tags and a timer tag with the timer name.
If nothing appears, the agent was offline, the flow failed to initialize, or the cron did not fire yet. Check the execution list for that flow.
Not this page
- A one-off tagged snapshot before a migration — Snapshot before a schema change.
- Cloud storage so another agent can restore the files — Restore across environments.
- Masking production columns in the flow — Mask Columns.