Skip to documentation
Screebits Docs
Flow Editor
Open Screebits
  • Screebits
  • Flow Editor documentation
  • Blueprints
  • Your first steps in Screebits
  • Workspace, strategies and account
  • Get started with the Flow Editor
  • Build an RSI Momentum Alert
  • Flow Editor concepts
  • How a strategy starts and continues
  • Control and data connections
  • Nodes, parameters, outcomes, and ports
  • Plans and feature availability
  • Saves, versions, and checkpoints
  • Tactical and Portfolio strategies
  • Validation and readiness
  • Flow Editor mode guides
  • Build Portfolio strategies
  • Build Tactical strategies
  • Flow Editor guides
  • Add a Quant Hub metric
  • Configure a node
  • Configure Settings and visual preferences
  • Connect nodes
  • Create a strategy
  • Create checkpoints and restore versions
  • Reset a Flow safely
  • Debug and replay a Backtest
  • Fix validation issues
  • Use keyboard shortcuts
  • Manage variables
  • Run a Backtest
  • Save and resolve conflicts
  • Work on tablet and mobile
  • Use Quick add
  • Use the Inspector
  • Add, move, duplicate, and remove nodes
  • Flow Editor examples
  • Portfolio rebalance with risk limits
  • Tactical order and position monitoring
  • Use Backtest Center
  • Read a Backtest result
  • Compare and export Backtests
  • Explore Quant Hub
  • Metric parameters, charts and overlays
  • Flow Editor node reference
  • Schedule Trigger
  • Flow Editor troubleshooting
  • Troubleshoot activation and validation
  • Troubleshoot Backtests and replay
  • Troubleshoot compact layouts
  • Troubleshoot connections and data types
  • Troubleshoot plans and locked features
  • Troubleshoot Quant Hub in the Flow Editor
  • Troubleshoot save, offline, and conflicts
  • Backtests and responsible use
  • Flow Editor glossary
  1. Screebits
  2. /Flow Editor documentation
  3. /Flow Editor node reference
  4. /Schedule Trigger
IntermediateLast verified Sep 30, 2026

Schedule Trigger

Starts a strategy on a recurring calendar schedule.

On this page
  1. When to use
  2. Example
  3. Choose an evaluation cadence
  4. Common problems
  5. Next steps

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.

Try it here

Explore Schedule Trigger

Starts a strategy on a recurring calendar schedule.

Exercise steps
  1. Change the schedule from weekly to monthly.
  2. Compare the day-of-week and day-of-month controls.
Schedule Trigger
Graph preview — a diagram of the example

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.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Schedule Trigger
Activation role
Primary activation
Category
Trigger
Availability
Portfolio only
Modes
Portfolio
Required plan
None
Behavior
Trigger
Control inputs
0
Output data types
datetime, period Info

Parameters

NameInput typeRequirementDefaultOptions and constraints
Schedule frequencySelection listRequiredweeklyOptions: Daily, Weekly, Monthly
WeekdaySelection listOptional when shownmondayOptions: Monday, Tuesday, Wednesday, Thursday, Friday; Shown when Schedule frequency is weekly
Last day of monthYes or noOptional when shownfalseShown when Schedule frequency is monthly
Day of monthNumberOptional when shown1Minimum: 1; Maximum: 28; Whole numbers only; Shown when Schedule frequency is monthly and Last day of month is not true
Cron expressionTextOptional when shownNot setShown when Schedule frequency is custom
Session anchorSelection listRequired when shownmarketOpenOptions: Market open, Market close, Custom time; Shown when Schedule frequency is one of daily, weekly, monthly
Custom timeTextRequired when shown09:30Shown when Schedule frequency is one of daily, weekly, monthly and Session anchor is customTime

Primary parameters

  • Schedule frequency
  • Weekday
  • Last day of month
  • Day of month
  • Session anchor
  • Custom time
  • Cron expression

Outcomes

  • On Schedule

Data inputs

None

Data outputs

  • Timestampdatetime
  • Periodperiod Info

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.

On this page

1 / 5
  1. When to use
  2. Example
  3. Choose an evaluation cadence
  4. Common problems
  5. Next steps

Practical guidance for strategies, historical simulations and metric research in Screebits.

Responsible useGlossary