​@JamieT Ensure the A360 extension is installed and active in Chrome. You may even try disabling it then re-enabling it to “reboot” the extension.

Also make sure the browser title *EXACTLY MATCHES* what you’re trying to capture. Even one character off and it won’t find the window.

Thanks for your suggestion.

I tried that and it didn’t work for me.

When I use the Control Room in Explorer and capture Chrome it works (earlier in my flow I open a new Chrome window).

I’ll stick to doing it this way for now.

Hi ​@JamieT ,

Few blockers can cause this kind of weirdness.

• Switch the Object Capturing technology in the Capture action (e.g., DOM vs. AI Sense) and recapture. Also reconfirm zoom is 100%. This combination has resolved “stuck capturing” for several users. 
• Multiple Chrome profiles: Make sure the Automation 360 extension is installed in the same Chrome profile you are automating. If your flow opens Chrome earlier, open with the same profile you use during design; mismatched profiles can stop the extension handshake (practical tip).
• Elevation mismatch: Don’t run Chrome as Admin while the Bot Agent/designer is non‑admin (or vice versa). UI frameworks block cross‑integrity injection (practical tip).
• After product upgrades: If the extension version gets ahead of/behind the recorder package, use the doc’s registry check to ensure it automation.bot.browseragent points to your Bot AgentAAChromeAgentManifest.json; if not, reinstall Bot Agent or run the provided installer scripts per your version. 

Here are Workarounds:

• Use wildcards/regex for window targeting

  In the Capture window, you can use * or a regex to match tabs whose titles change each load. This is far more reliable than exact title matching. 

• Disambiguate tabs with the same title

  When multiple tabs share the same title (very common with PDFs), use Window → Set title to temporarily rename the active tab and then capture/act against that unique title. This is a supported pattern; it helps the recorder “find the right tab.”  

Note: If someone used Chrome’s More tools → Name window… feature, there’s a known limitation that can confuse automation; avoid or reset that naming while running the bot.

• Prefer actions that don’t depend on the title

  For closing PDF tabs spawned by your ERP, consider:

  • Keyboard: Ctrl+W on the active tab (after a Window → Activate).
  • Or a Browser → Close tab action (if available) or “switch to tab by URL contains” if the PDF viewer path is stable.
    These avoid title matching altogether (no external doc needed here—practical tip).