strategy-startup-guardrails

Prevent OpenAlgo strategy startup crashes by validating imports, time module usage, environment configuration, and data readiness before launch. Guardrails check for shadowed time modules, verify broker credentials, and ensure master contracts are downloaded to stop failures before deployment.

Strategy crashes after restart often occur because master contracts are missing or environment variables like OPENALGO_APIKEY are not loaded. Running startup triage validates these configurations and performs preflight history checks to identify and resolve missing data or credentials.

The best way to triage startup failures is running guided guardrails that diagnose import patterns, time module usage, and environment configuration gaps. This fast triage provides actionable steps to verify configs and ensure required master contracts are downloaded for recovery.

Yes, master contracts must be downloaded for required exchanges and symbols before running a strategy startup preflight. Preflight data checks verify this readiness along with environment configurations to ensure a safe launch and prevent immediate crashes.

Yes, startup guardrails verify environment configuration by checking if OPENALGO_APIKEY and broker credentials are present. Env/config validation ensures these required variables are available before the strategy attempts to launch.

Validating time module usage stops strategy crashes by preventing shadowing of the time module and enforcing safe usage patterns. Import pattern checks detect conflicting declarations that cause unpredictable failures during script execution.