A batch is stuck or failed

In the dashboard, a running batch shows a progress indicator. If the indicator hasn’t moved in 30+ minutes for a moderate catalog, it’s worth investigating.

Some normal-looking pauses:

• Slow start — large catalogs spend the first few minutes preparing the queue. The progress bar may sit at zero before suddenly jumping ahead.
• Platform rate limits — each platform throttles API writes, so a large batch can stall in bursts while CataSEO waits out the limit.
• Token throttling — if your batch hits your token allocation, it pauses cleanly. That’s not “stuck” — it’s “out of tokens.”

• Wait a few more minutes for slow starts and large catalogs.
• Check your token balance — a stalled batch may simply be out of tokens.
• Check your store connection — a disconnected store also stops a batch. See Reconnect your store.
• Open the failed products tab if the batch finished with errors. Each error has a reason and you can re-run failed products individually with express tokens.

CataSEO automatically retries transient failures (network glitches, momentary platform 500s) for each product in the batch. Persistent failures get logged and the batch continues with the next product — one bad product doesn’t kill the whole job.

If you need to stop a running batch, contact support. Tell us your store and we’ll cancel it from our side.

You’ll get an email titled with your store name showing:

• Products optimized
• Errors (if any)
• Remaining batch token balance

The same numbers are visible in the dashboard.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.