Understanding OTTO Autopilot Bulk Deployment Limits

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

Overview

When using OTTO SEO's Autopilot feature, deployments are processed in batches rather than all at once. If you have noticed that not all of your pending improvements were deployed in a single run, this is expected behaviour — Autopilot applies changes in grouped batches to protect site stability and allow incremental review.

Why Batch Limits Exist

The batch limit is designed with your site's health in mind. Deploying a very large number of changes simultaneously can:

  • Overwhelm your CMS or hosting environment with simultaneous write requests.
  • Make it harder to identify which specific change caused an issue if something goes wrong.
  • Slow down your site temporarily during the deployment window.

By processing in batches, OTTO gives your server time to handle each group of changes and gives you a clear checkpoint to review results before continuing.

What to Do If Not All Improvements Were Deployed

If you find that some improvements were not deployed during a run, the specific batch size and exact triggers depend on your project configuration and are managed on the backend. Here is what you can do:

  1. Navigate to OTTO SEO and open the relevant site project.
  2. Check which improvements are still marked as pending after the most recent deployment run.
  3. Note the exact number of improvements that were deployed versus the total number that were pending, so you have this information ready.
  4. If improvements remain pending and are not being picked up in subsequent runs, contact our support team — provide your project name, the number of improvements pending, and the date and time of the last deployment run so our team can investigate your project's queue and batch configuration directly.

Tips for Managing Large Deployments

  • Prioritise improvements by impact: Review your pending improvements and ensure your highest-priority items are approved and ready first.
  • Monitor each run: After each Autopilot run, revisit your project dashboard to confirm how many improvements were applied and how many remain.
  • Escalate stalled queues promptly: If your remaining improvements are not being processed across multiple runs, this may indicate a configuration issue that requires backend investigation — reach out with the details listed above so our team can resolve it quickly.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.