Search Atlas Help Center

🔧 Fix OTTO Deployments Turning On and Off

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🧭 Overview

If your OTTO deployments are switching on and off on their own, getting stuck, or failing to stay active, this article walks you through the four most common root causes and how to fix each one. Follow the diagnostic steps below in order to identify your specific issue quickly.

🔍 Step 1 — Confirm the Symptom

Before troubleshooting, identify exactly what you are seeing. This helps pinpoint the right fix.

  • Deployments toggle off shortly after turning on — likely a script reinitialization loop or Cloudflare conflict.
  • Deployments appear active but changes are not applied — likely a task queue delay.
  • Deployments turn on but revert after a few minutes — likely a permission or CMS sync failure.
  • Deployments stay stuck in a loading or processing state — likely a task queue backlog.

⏱️ Cause 1 — Task Queue Processing Delays

OTTO processes deployments through a background task queue. During high-traffic periods or after bulk changes, tasks can back up and cause deployments to appear inactive or to cycle on and off as tasks retry.

How to resolve:

  1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar (URL: /seo-automation-v3).
  2. Open the affected site and check the deployment status indicator. If it shows a spinning or pending state, the queue is still processing.
  3. Wait 5–10 minutes and refresh the page. Do not toggle the deployment off and on again during this time, as repeated toggling adds more tasks to the queue and worsens the delay.
  4. If the stuck state persists beyond 15 minutes, disable the deployment once, wait 2 minutes, then re-enable it to force a fresh task entry.

☁️ Cause 2 — Cloudflare Integration Configuration Issues

If your site uses Cloudflare, certain settings can conflict with OTTO's script delivery and cause deployments to deactivate intermittently. The most common culprits are aggressive caching rules, Rocket Loader, and Bot Fight Mode.

How to resolve:

  1. Log in to your Cloudflare dashboard and navigate to the Speed section for your domain.
  2. Disable Rocket Loader. This feature asynchronously loads JavaScript and can prevent OTTO's deployment script from initializing correctly.
  3. Go to Security → Bots and temporarily disable Bot Fight Mode. OTTO's script requests can be misidentified as bot traffic, causing the connection to drop.
  4. In Caching → Configuration, set the caching level to Standard and ensure that the page rule or cache rule covering your site does not cache HTML responses aggressively.
  5. If you use Cloudflare Workers or Page Rules that rewrite or redirect URLs, verify they do not intercept the OTTO script endpoint (/_otto/ paths).
  6. After making changes, purge your Cloudflare cache and re-enable the OTTO deployment in Search Atlas.

🔁 Cause 3 — Script Installation or Reinitialization Loops

A reinitialization loop occurs when the OTTO script is installed, then detected as conflicting with another script or plugin, removed automatically, and then reinstalled — causing a visible on/off cycle. This is most common on WordPress sites with security or performance plugins.

How to resolve:

  1. In your WordPress admin panel, check for plugins that manage or block external scripts, such as security hardening plugins, script managers, or cookie consent tools.
  2. Temporarily deactivate these plugins one at a time, re-enable the OTTO deployment after each deactivation, and observe whether the toggling stops. This isolates the conflicting plugin.
  3. Once identified, whitelist the OTTO script domain (cdn.searchatlas.com) in that plugin's settings instead of keeping it deactivated.
  4. Verify the script is only installed once. Go to OTTO SEO → All Sites (SEO Automation) → your site → Deployment Settings and confirm there is no duplicate script entry. If you previously installed the OTTO snippet manually in your theme files, remove it to avoid a double-installation conflict.

🔐 Cause 4 — Permission or CMS Sync Failures

OTTO requires continuous write access to your CMS to apply and maintain changes. If the connected account's permissions are revoked, expire, or fall out of sync, deployments will revert or toggle off automatically.

How to resolve:

  1. Go to OTTO SEO → All Sites (SEO Automation) in the left sidebar and open the affected site.
  2. Navigate to Avatar (top-right) → Settings → CMS Connectors and review the connected CMS credentials.
  3. If you see a warning icon or a Reconnect prompt, click it and re-authenticate with your CMS account. Use an account that has Administrator-level permissions.
  4. If no warning is shown but the issue persists, disconnect the CMS integration, save, then reconnect and re-authenticate from scratch to force a full credential refresh.
  5. After reconnecting, re-enable the deployment and monitor it for 10 minutes to confirm it holds its active state.

✅ Quick Diagnostic Summary

  • Spinning/stuck state for under 15 min → Wait for queue to clear.
  • Toggles off immediately after enabling → Check Cloudflare Rocket Loader and Bot Fight Mode.
  • Cycles on and off repeatedly every few minutes → Check for conflicting plugins causing a script loop.
  • Reverts to off after 5–10 minutes → Reconnect CMS credentials with Administrator access.

💬 Still Need Help?

If you have worked through all four causes and the intermittent toggling continues, gather the following details before reaching out: your site URL, the approximate time the toggling started, and any recent changes made to your CMS, Cloudflare settings, or plugins. 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.