A message batch page follows one existing Communication request. Open it from that request’s activity link with permission to view the associated workspace. The link reads Open this request’s activity and opens the page in a new tab; open the existing request through the application rather than guessing its identifier.
Read the request state
- Check the request’s submitted time, timezone and latest results-check time. Provider results have not been checked yet is an explicit unknown state.
- Compare selected recipients with those handed off for dispatch and not dispatched. A handoff count does not mean a provider accepted the messages.
- Review provider-accepted, delivered, failed and canceled counts separately. Inspect Recipient results for individual state differences; do not convert an unconfirmed result into failure or success.
- Use Refresh request status to check the existing request. Unconfirmed attempts are retained and are not resent automatically.
- If authorized to change remaining work, use Pause remaining, Resume queue, or Cancel remaining. Already dispatched messages may still finish. These controls affect live queue behavior, not just the display.
- If admission was never confirmed, review the distinct Cancel unconfirmed request option. A closed-before-admission result explicitly says no recipient job was created by that request.
Confirm and recover
The page states that dispatch is paced and accepted-for-dispatch is not delivered. Check the latest status after a control request; do not submit a new batch simply because the current one is slow. If a control outcome is unconfirmed, refresh this same request and seek support if it remains unclear. Back to Communication returns to the workspace without proving that queued work stopped.
Related: Communication, Support.