Why is my Apify actor under maintenance?

Maintenance flags are applied by Apify's automated quality system when your actor consistently fails certain checks over a multi-day period. The most common causes are: dataset schema mismatches between your declared schema and actual output, low success rates (below approximately 80% over 7 days), crashes on default input, and stale builds that have not been updated in 90+ days. Here is how to diagnose which specific issue triggered your maintenance flag. First, check the Apify Console for any automated run results — Apify periodically runs your actor with its default input to verify it works. If these automated runs are failing, that is likely the trigger. Second, use the ApifyForge Schema Validator to check for schema mismatches — this is the most common cause and the easiest to miss because your actor might work perfectly while producing output that does not match its declared schema. Third, check your success rate in the ApifyForge dashboard — even occasional failures can drag your 7-day rolling average below the threshold. To resolve a maintenance flag, you need to fix the underlying issue and then demonstrate consistent successful operation. Here is the process. Identify the cause using the steps above. Fix the issue — update your schema, fix the bug, handle the edge case, or rebuild with updated dependencies. Push a new build to Apify. Run your actor successfully with the default input several times to rebuild your success rate. Wait for Apify's periodic re-evaluation — the flag does not clear instantly, it typically takes several days of clean runs. Prevention is far more effective than remediation. Use the ApifyForge Schema Validator before every push to catch schema mismatches. Use the Test Runner to verify your actor works with default input. Use Cloud Staging to confirm production behavior matches local testing. Monitor your fleet health in the dashboard to catch declining success rates before they trigger flags. For more details on testing workflows, see the questions about the Schema Validator, Test Runner, and Cloud Staging.