When a vendor has an outage or starts rejecting a template, you’re left with a batch of failed messages your clients still need delivered. Repush resends them over a different route. You can repush one message from the Message Log, or run a bulk repush filtered by user, error code and time window.
Option A: Repush a single message
- Open Message Log and find the failed message.
- In the Status tab, click Repush. The button only appears on failed messages.
- In the Single Message Re-push window, choose a route under Select Route for Re-push.
- Click Send.
Use this for one-off client complaints (“my OTP to this number failed”).
Option B: Bulk repush
Open the Re-push menu → Repush Messages.
| Filter | Notes |
|---|---|
| Product | SMS is selected by default |
| Username | The client whose messages you’re repushing |
| Date and time range | Today only. Defaults to 12:00 AM–11:59 PM; narrow it to the outage window |
| Global Error Code | Success codes can’t be selected |
| Vendor Error Code | Optional; use it to target one vendor’s specific failure |
| Connects | Limit to the connect that failed |
| Transaction ID | Optional |
| Sender ID | SMS only, optional |
| Repush Route | Required: the route that will carry the resend |
Repush always runs in two steps:
- Get Summary: shows how many messages match your filters. Nothing is sent yet.
- Repush: runs the job. It runs in the background, and progress appears in Repush History (status, progress counts, filters used, route, request and completion times).
Before you run a large repush
- Check the repush route has a working template. For India DLT traffic, the new route must carry the same PE ID/template, or every message will fail again.
- Time matters. For OTPs and time-sensitive alerts, a resend hours later does more harm than good. Filter those sender IDs out, or leave them.
- Run a small batch first. Repush one username for a narrow time window, then check Message Log and the user’s credit before repushing everything.
- Fix the cause first. If the failure was caused by your own mapping or routing, fix that before repushing, or the retry will fail the same way.
Error messages
- “SMS repush URL is not configured” or “repush not enabled”: the repush service isn’t enabled on your installation. Contact SMPPCenter support.
- “Success error code cannot be used for repush”: you selected a delivered/success code. Choose a failure code.
Repush vs automatic retry
Repush is a manual step for recovering after an incident. For automatic failover while traffic is flowing, use route-level retries (the Routes Multiple Retry plugin allows up to 4 retries across different routes), so fewer messages need repushing in the first place.
Related articles
- How to Repush Delivery Reports (DLRs) to Your Clients
- Do the Failed Messages Get Retried in SMPP Client?
- How to Map Vendor Error Codes to Global Error Codes
Found this useful?Add as Preferred Source on Google