Troubleshoot Astronomer production deployments with Astro CLI. Use when investigating deployment issues, viewing production logs, analyzing failures, or managing deployment environment variables.

Astro Deployment Troubleshooting This skill helps you diagnose and troubleshoot production Astronomer deployments using the Astro CLI. For deployment management , see the managing astro deployments skill. For local development , see the managing astro local env skill. Quick Health Check Start with these commands to get an overview: Viewing Deployment Logs Use c to control log count (default: 500). Log flags cannot be combined — use one component or level flag per command. Component Specific Logs View logs from specific Airflow components: Log Level Filtering Filter by severity: Search Logs Search for specific keywords: Complete Investigation Workflow Step 1: Identify the Problem Look for: Status: HEALTHY vs UNHEALTHY Runtime version compatibility Resource limits (CPU, memory) Recent deployment timestamp Step 2: Check Error Logs Look for: Recurring error patterns Specific DAGs failing repeatedly Import errors or syntax errors Connection or credential errors Step 3: Review Scheduler Logs Look for: DAG parse errors Scheduling delays Task queueing issues Step 4: Check Worker Logs Look for: Task execution failures Resource exhaustion Timeout errors Step 5: Verify Configuration Look for: Missing or incorrect environment variables Secrets configuration (AIRFLOW SECRETS BACKEND) Connection configuration Common Investigation Patterns Recurring DAG Failures Follow the complete investigation workflow above, then narrow to the specific DAG: Resource Issues Configuration Problems Import Errors Environment Variables Management List Variables Create Variables Update Variables Delete Variables Note : Variables are available to DAGs as environment variables. Changes require no redeployment. Key Metrics from deployment inspect Focus on these fields when troubleshooting: status : HEALTHY vs UNHEALTHY runtime version : Airflow version compatibility scheduler size/scheduler count : Scheduler capacity executor : CELERY, KUBERNETES, or LOCAL worker queues : Worker scaling limits and types min worker count , max worker count worker concurrency worker type (resource class) resource quota cpu/memory : Overall resource limits dag deploy enabled : Whether DAG only deploys work current tag : Last deployment version is high availability : Redundancy enabled Investigation Best Practices 1. Always start with error logs Most obvious failures appear here 2. Check error logs for patterns Same DAG failing repeatedly? Timing patterns? 3. Component specific troubleshooting : Worker logs → task execution details Scheduler logs → DAG processing and scheduling Webserver logs → UI issues and health checks Triggerer logs → deferrable operator issues 4. Use keyword for targeted searches More efficient than reading all logs 5. The inspect command is your health dashboard Check it first 6. Environment variables in inspect output May reveal configuration issues 7. Log count default is 500 Adjust with c based on needs 8. Don't forget to check deployment time Recent deploy might have introduced issue Troubleshooting Quick Reference Symptom Command Deployment shows UNHEALTHY astro deployment inspect <ID + error logs DAG not appearing error logs for import errors, check scheduler logs Tasks failing workers logs + search for DAG with keyword Slow scheduling scheduler logs + check inspect for scheduler resources UI not responding webserver logs Connection issues Check variables, search logs for connection name Import errors error keyword "ImportError" + scheduler logs Out of memory inspect for resources + workers keyword "memory" Related Skills managing astro deployments : Create, update, delete deployments, deploy code managing astro local env : Manage local Airflow development environment setting up astro project : Initialize and configure Astro projects

troubleshooting-astro-deployments