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
  • Read Engine State
  • 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. /Read Engine State
IntermediateLast verified Sep 30, 2026

Read Engine State

Exposes an available read-only engine value as data.

On this page
  1. When to use
  2. Example
  3. Observe without changing state
  4. Common problems
  5. Next steps

Exposes an available read-only engine value as data.

When to use

Use it when strategy logic needs supported current execution context without maintaining a separate variable.

Example

Read an available account or execution-state value and feed it to a comparison.

Try it here

Explore Read Engine State

Exposes an available read-only engine value as data.

Exercise steps
  1. Choose another engine-state path in Inspector.
  2. Inspect the resolved output type and compare it with a user variable.
Event TriggerRead Engine State
Graph preview — a diagram of the example

Observe without changing state

Choose a supported path such as $engine.portfolio.equity and connect its Value output to a compatible comparison. If an illustrative run starts with equity 10,000 and a later state reports 9,500, a separate Expression can calculate the change, provided it receives both values from valid sources. Read Engine State supplies a snapshot value from the current execution context; it does not set equity, guarantee that every path is available, or create a market event. Confirm the selected path, type and unit before comparing it with a literal threshold.

Common problems

Only the values offered by the node are supported. The state is read-only, and this node does not continue control flow.

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
Read Engine State
Activation role
No activation role
Category
Data
Availability
Tactical and Portfolio
Modes
Tactical and Portfolio
Required plan
None
Behavior
Provides a value
Control inputs
0
Output data types
any

Parameters

NameInput typeRequirementDefaultOptions and constraints
Engine stateTextRequiredNot setNone

Primary parameters

  • Engine state

Outcomes

None

Data inputs

None

Data outputs

  • Valueany

Related documentation

  • ConditionCompares values and selects Match or No Match.
  • ExpressionCalculates a numeric formula from connected inputs.
  • Control and data connectionsUse control connections to continue execution and data connections to pass compatible values.

On this page

1 / 5
  1. When to use
  2. Example
  3. Observe without changing state
  4. Common problems
  5. Next steps

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

Responsible useGlossary