Schedule Trigger
Starts a strategy on a recurring calendar schedule.
Starts a strategy on a recurring calendar schedule.
When to use
Use it when portfolio evaluation should run at a defined cadence rather than from a market tick.
Example
Start a monthly allocation path and use the connected period information in downstream scheduling logic.
Choose an evaluation cadence
Schedule Trigger is the primary activation of a Portfolio graph. For a weekly example, choose Weekly, Monday, and the available session anchor or time setting appropriate to the data you test. Connect On Schedule to the portfolio decision path, and use the Period data output only where a downstream node expects period information. For a monthly process that must include months of different lengths, use the supported last day of month setting instead of assuming every month has day 31.
The visible Custom frequency is reserved rather than an authorable schedule. Check the selected market session and time reference in the Inspector and validate the graph before a historical run. Another Schedule Trigger on the same primary path does not solve a missing data input; Portfolio uses one primary scheduled activation, with a separately constrained Safety Trigger when a guard is needed.
Common problems
An invalid schedule or timezone can make timing differ from expectations. Keep only one primary activation.
Next steps
Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.
Related documentation
- How a strategy starts and continuesUnderstand primary activation, control outcomes, and why data alone does not execute an action.
- Build Portfolio strategiesDesign a scheduled or safety-driven graph that selects assets, calculates weights, applies limits, and rebalances.
- Period FieldExtracts one field from schedule period information.