Development preview — not released

Keep Control When a Task Is Interrupted

Planned workflow: Pause new actions, preserve local progress, and review uncertain results before continuing. Browser restarts and account changes require careful recovery.

Will an interrupted task restart Instagram writes automatically?

A restart must reconcile persisted state, actor identity, preview validity and uncertain outcomes before resuming. An unknown write cannot be blindly retried. Internal recovery behavior is tested separately from live Instagram compatibility, which remains unverified.

Pause versus Stop and Force Stop

Pause keeps a task available for explicit continuation. Stop and Force Stop prevent future dispatches, but neither guarantees reversal of a request already sent.

Resume after a browser restart

A browser restart requires state reconstruction from IndexedDB and review of in-flight actions. Alarms are wakeup signals, not a promise of uninterrupted background execution.

Check an unknown result

For an uncertain write, inspect the current relationship before deciding what happened. Do not automatically resend a Follow or Unfollow because its response was lost.

Keep account data separate

Start, Resume, and Dispatch must compare the current actor with the task actor. An account switch moves the task to review rather than continuing under another identity.

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

View release status