Help center › Data and Interfaces
Scheduled jobs
One cron line runs the scheduler every minute; jobs scan the drop box, move the start-of-day chain, run checks, write files and clean up.
At a glance
- Where
- System › Data and Interfaces › Scheduled jobs (
/app/feeds/jobs) - Who
- Operations and Admins; Operations can run a job now, pause and resume it. Roles and permissions
Try it in the demo A private sandbox firm, no sign-up. Simulated data only.

One cron line runs the scheduler every minute, with a lock so two runs never overlap. Jobs use cron expressions in New York time, can follow the business calendar (skipped on weekends and US holidays) and a run window, retry with growing waits, and keep their history.
| Job | Schedule (New York) | What it does |
|---|---|---|
| Scan inbound files | every minute | Looks for new files in the drop box, checks late and missed feeds. |
| Start-of-day chain | every 5 minutes, 04:00–11:30 on business days | Moves the chain forward as feeds are applied. |
| Data quality checks | 07:15, 12:15, 16:15 on business days | Runs the data-quality detectors. |
| End-of-day trade file | 16:30 on business days | Writes the day's simulated trades to outbound (when switched on). |
| Daily operations summary | 17:45 on business days | Emails the day's feed and start-of-day summary to Operations. |
| Retention clean-up | 03:20 every day | Deletes archived and rejected files past their retention. |
The demo sandbox has no scheduler: nothing runs on its own and files arrive when you simulate them.
Related articles
Do it with the API
Every action on this screen can also be done by your own systems, under the same permissions. See Authentication to get a token.
- GET
/api/v1/schedulesScheduled jobs and their last runs
Paper trading only: orders and fills in Vestoris are simulated. Nothing here is investment advice.