Understand delivery statuses and replay

Read Activity clearly, fix the cause, and replay only when it is safe.

Results and Data
Written forExperience managers and data managers

Integrations > Activity is the delivery record for connected destinations and webhooks. Most temporary failures retry on their own. Manual replay is for a fixed permanent problem, restored paused work, or a carefully verified uncertain result.

Steps

  1. 1Open Integrations and select Activity.
  2. 2Use All, Needs attention, or Skipped to narrow the list, then open the delivery you are investigating.
  3. 3Read the destination, event, attempt count, next attempt, and last error before changing anything.
  4. 4For Retrying, wait for the shown next attempt unless the destination has already recovered and the send is urgent.
  5. 5For Action needed, fix the connection, mapping, or receiver response first, then replay the delivery.
  6. 6For Needs verification, check the receiving service for the original lead before replaying. Confirm replay only when the original result is absent.
  7. 7For sending disabled, restore the destination or integration switch before replaying the paused delivery.
  8. 8After replay, refresh Activity and confirm Delivered. Check the receiving service once more for duplicates.

What to know

  • SendingThe delivery is waiting or currently being sent. Recent rows normally need no action.
  • DeliveredThe destination accepted the delivery. If the record is hard to find, search using the lead email and event time before replaying anything.
  • RetryingA temporary provider, receiver, or network failure occurred. Snapbar schedules another attempt automatically.
  • Action neededThe failure is permanent until a person fixes its cause. Common causes include expired access, invalid field setup, or a receiver rejecting the request.
  • Needs verificationSnapbar cannot prove whether the receiver completed the original request. Replaying without checking can create a duplicate.
  • Skipped with reasonThe lead lacked the required consent or contact detail, or sending was disabled. A consent skip should remain skipped. Work paused by a disabled destination or switch can be replayed after it is restored.

Tips

  • Fix the cause before replaying a failed delivery.
  • Restore paused destinations before replaying disabled work.
  • For uncertain outcomes, ask the destination owner to confirm the original result is absent.

Related articles

Still need help?

Tell us the experience name and what you were trying to do, and our team will pick it up from there.

Email ops@thesnapbar.com