Development preview — not released

Resolve a Paused Task

Planned workflow: Find the reason a task stopped dispatching actions, from daily limits to session changes. Check uncertain results before deciding how to continue.

How should I handle a paused task or an unknown write?

Read the pause reason before resuming: actor mismatch, stale preview, missing entitlement and platform restrictions need different fixes. Revalidate the current actor. An unknown write needs reconciliation, not a blind retry; Stop does not undo an already sent Instagram operation.

Daily limits and cooldowns

A quota pause waits for allowance or reset; a cooldown waits for the configured time. Neither is the same as a failed Instagram request.

Session changes and platform challenges

An actor mismatch or platform challenge needs review. Continue only after the current actor matches the task; no subscription can authorize bypassing a challenge.

Unknown results and recovery

Unknown retains the write guard and its quota reservation. Recovery should inspect evidence once and must not automatically retry a write whose outcome is unresolved.

Storage and compatibility issues

Storage pressure and unsupported source behavior need separate remedies. Export or back up data where possible and keep safety records while diagnosing the issue.

Official sources & scopeChrome: storage and cookies — Local extension storage and service workersChrome: extension service worker lifecycle — Worker termination and persistent state

These sources explain platform behavior. Product-specific scope and limits come from our implementation registry; they are not an endorsement by Instagram, Google, or Stripe.

Current Instagram settings and live source behavior are not yet verified. These links support only the topics named beside them.

Your next step

Browse relevant help