You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
brb, going to make a PR and ship an update. I didn't realize we didn't expose the timestamp in the new API.
recurring on a cron schedule
we don't have the cron scheduler built yet, but in the meantime, you can use a library like node-cron (or even GitHub Actions or AWS EventBridge) to trigger the workflow.
something like this:
import{CronJob}from"cron";import{myWorkflow}from"./openworkflow/my-workflow";CronJob.from({cronTime: "* * * * *",// every minutestart: true,// run immediatelyonTick: asyncfunction(){awaitmyWorkflow.run({ ... });// start your workflow},});
Thanks for the bump @lecramr, and sorry @thomasjiangcy for missing your previous comment.
Schedules will be in the upcoming OpenWorkflow server. Cron really needs a coordinator and I don’t want to ship a version on raw SQLite/Postgres that makes workflow/other DB usage performance worse.
For now, I’d recommend an external cron (Node cron, GitHub actions, Vercel cron, k8s job, etc) -> hit your api -> ow.runWorkflow().
Activity
jamescmartinez commentedon Feb 4, 2026
agreed on both fronts.
brb, going to make a PR and ship an update. I didn't realize we didn't expose the timestamp in the new API.
we don't have the cron scheduler built yet, but in the meantime, you can use a library like node-cron (or even GitHub Actions or AWS EventBridge) to trigger the workflow.
something like this:
jamescmartinez commentedon Feb 4, 2026
scheduling just shipped in openworkflow v0.6.4
[-]Support for scheduled (one shot) and recurring workflows[/-][+]Support for recurring workflows[/+]jamescmartinez commentedon Feb 4, 2026
going to keep this issue open, so I updated the issue title to reflect what's not yet implemented
gsxdsm commentedon Feb 4, 2026
Thanks! Can't wait for built-in cron support!
thomasjiangcy commentedon Feb 21, 2026
Just checking in to see if any help is required for the recurring piece! Would love to have this implemented.
lecramr commentedon May 11, 2026
Same for me, too! If there is already a plan how to achieve the implementation, I'd love to contribute :)
jamescmartinez commentedon May 11, 2026
Thanks for the bump @lecramr, and sorry @thomasjiangcy for missing your previous comment.
Schedules will be in the upcoming OpenWorkflow server. Cron really needs a coordinator and I don’t want to ship a version on raw SQLite/Postgres that makes workflow/other DB usage performance worse.
For now, I’d recommend an external cron (Node cron, GitHub actions, Vercel cron, k8s job, etc) -> hit your api ->
ow.runWorkflow().jamescmartinez commentedon Oct 12, 2026
quick update: I changed the approach since my last comment. This is shipping in openworkflow@0.11 later today without a server required.
Schedules are stored in SQLite/Postgres, and your existing workers coordinate through the database to create runs.
The implementation is in #892
thanks @gsxdsm @thomasjiangcy @lecramr for your patience!
jamescmartinez commentedon Oct 12, 2026
@gsxdsm @thomasjiangcy @lecramr live now in openworkflow@0.11!
docs: https://openworkflow.dev/docs/schedules
thanks again for your patience. would love to hear how it works for you