Skip to main content
The Schedule node fires a trigger on a recurring interval while a blueprint is deployed. Use it when a strategy should evaluate predictably instead of reacting to every market tick. For example, pair Schedule with a Market node and a Comparison node to check a condition every minute.

​
Supported schedule

Schedule currently supports interval mode only. Cron expressions are not supported for deployed runtime execution yet. The interval must be at least 1 second. Existing blueprints with invalid or legacy schedule configuration need to be updated before deploy validation will pass.

​
Runtime behavior

Each deployed blueprint gets its own schedule subscription. Starting, stopping, or redeploying one blueprint does not share the timer with another deployment. Schedule triggers repeat over time, so terminal nodes like notifications, webhooks, and trades can run more than once. Use a Rate Limiter node upstream when you need to cap repeated terminal actions.