Plans and feature availability
Recognize plan locks, current availability, read-only states, and validation issues.
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.
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.