LinkStackHelp Center
Log in

Rerun automations skipped at your monthly limit

Find eligible Instagram runs skipped for lack of automation capacity, request a rerun, and check the delivery result.

3 min read
Cream message cards waiting at a lavender gate beside a clock, with a hand opening the gate.
Illustration: recovery needs both available capacity and time left to reply.
In this article

Find the skipped runs that can still run

This recovery is for runs skipped because your automation allowance was exhausted. Other skipped or failed messages need their own diagnosis. The count can shrink as reply windows expire.

  1. Open Automations → Activity → Skipped. Look for the recovery card and its eligible count.
  2. Read Earliest window closes. LinkStack checks Instagram comment private replies within seven days of the comment and DM or story replies within 24 hours of the original inbound event. Instagram Live comments are excluded.
  3. Check your current automation capacity. If the card shows Upgrade to rerun, use it to review your options. Upgrading alone does not rerun anything.
Skipped activity with three eligible automations, an earliest deadline, and Rerun skipped automations.
Sample activity: three skipped runs are still within their reply windows. Check the deadline before rerunning.

Request a rerun while capacity is available

Retrying keeps the original event time. It never restarts the reply window. Current workflow rules, repeat-trigger guards, pauses, AI credits where needed, and provider checks still apply.

  1. Check that the automation is active and its Instagram account is connected. Review any contact pauses or workflow changes that could affect the reply.
  2. Choose Rerun skipped automations. LinkStack requests up to 50 eligible runs in one batch and checks capacity again as work is admitted.
  3. Read the result. Reruns queued means the request was accepted for processing. It does not confirm that a message was sent.
Reruns queued confirmation with Refresh activity and instructions to check Activity for results.
Queued confirms the request was accepted. Refresh Activity to check subsequent results. This sample did not send messages.

Check what happened after the request

  1. Choose Refresh activity and inspect the subsequent run or delivery result. The original skipped record remains in the history.
  2. If only part of a batch queued, read the failed or unavailable counts. Retry the remaining eligible work when offered; do not assume the full batch ran.
  3. If more eligible runs remain, request another batch while capacity and reply windows allow it.
  • A deadline can expire between opening the page and requesting recovery. An expired event cannot be recovered through this action.
  • A disconnected account, inactive automation, deleted comment, contact pause, exhausted AI credits, or delivery error can still stop a reply. Fix the reason shown in Activity.
  • If no recovery card appears, there may be no eligible quota-skipped runs left. A larger plan cannot make an expired event eligible again.

Related articles

Still need help?

Support & feedback