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
  • 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 concepts
  4. /Plans and feature availability
All levelsLast verified Aug 23, 2026

Plans and feature availability

Recognize plan locks, current availability, read-only states, and validation issues.

On this page
  1. Plan lock
  2. Catalog availability
  3. Read-only and transient states
  4. Validation is separate

A feature can be unavailable for several reasons. The recovery depends on the reason shown in the product.

Plan lock

A plan lock means your current plan does not include the mode, node, capacity, or action. Review the current plan information shown in the product before upgrading. Limits can change, so this documentation does not copy numeric quotas.

Try it here

Distinguish availability states

Recognize plan locks, current availability, read-only states, and validation issues.

Exercise steps
  1. Switch between the illustrative Free access scenario and the unrestricted teaching palette.
  2. Inspect the disabled controls and their explanations. Actual account availability is checked in the product.
Event TriggerData SourceIndicatorConditionAlert
Graph preview — a diagram of the example

Catalog availability

Quant Hub metrics and similar resources can have their own state and minimum plan. A resource that is absent or disabled in the picker may not be available in the Flow Editor, even when the general feature is visible.

Read-only and transient states

Historical preview and replay can make the editor read-only. Saving, offline, conflict, or loading states can temporarily disable an action. These states do not necessarily require a plan change.

Validation is separate

A validation issue describes the graph you built. Resolve it by changing configuration or connections. A plan lock must be resolved through availability, not by rewiring the graph.

Related documentation

  • Troubleshoot plans and locked featuresDistinguish a plan requirement from a validation problem, catalog restriction, or read-only state.
  • Validation and readinessDistinguish blocking errors from guidance and make a graph ready before testing it.
  • Add a Quant Hub metricSelect an available metric version and use its value in the graph.

On this page

1 / 4
  1. Plan lock
  2. Catalog availability
  3. Read-only and transient states
  4. Validation is separate

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

Responsible useGlossary