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 troubleshooting
  4. /Troubleshoot plans and locked features
All levelsLast verified Aug 23, 2026

Troubleshoot plans and locked features

Distinguish a plan requirement from a validation problem, catalog restriction, or read-only state.

On this page
  1. A mode or node is locked
  2. A resource is absent
  3. The editor is read-only
  4. Validation still fails

Use the visible reason before deciding that an upgrade is required.

A mode or node is locked

Open the availability information shown with the control. It identifies the required plan or capacity. Use the current plan details shown in the product; this documentation does not repeat numeric quotas.

Try it here

Distinguish availability states

Distinguish a plan requirement from a validation problem, catalog restriction, or read-only state.

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

A resource is absent

A Quant Hub metric or similar resource can be unavailable because of its state, data definition, or required plan. Search the picker and read disabled-result guidance. General access to a feature does not make every resource available in the editor.

The editor is read-only

Historical preview and full replay are intentionally read-only. Return to the current version to edit. Loading, saving, offline, and conflict states can also disable actions temporarily.

Validation still fails

An upgrade does not repair graph structure. Resolve missing parameters, invalid connections, cycles, and activation problems separately.

Related documentation

  • Plans and feature availabilityRecognize plan locks, current availability, read-only states, and validation issues.
  • Troubleshoot Quant Hub in the Flow EditorRecover when QHM Metric Value is absent, a metric cannot be selected, or its saved identity needs repair.
  • Troubleshoot Backtests and replayRecover from blocked Backtest launch, preview or submission errors, and unavailable full replay.

On this page

1 / 4
  1. A mode or node is locked
  2. A resource is absent
  3. The editor is read-only
  4. Validation still fails

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

Responsible useGlossary