Troubleshoot an Android SMS Gateway Without Duplicate Sends
By Zoril SMS team · Published
Start with the last known message state. Repeatedly pressing Send can create duplicates and makes a gateway fault harder to diagnose.
1. Confirm account and queue status
Check the active organisation, plan/trial status, credits and daily limits. Review Gateway Status for queue age and Campaigns for progress and errors. If a limit is blocking sends, use the displayed reset information or ask the administrator to review the plan.
2. Check the phone connection
Use https://sms.zoril.app in the gateway app. Confirm internet, power, required permissions, foreground service and battery optimisation settings. Reconnect with the existing device identity; deleting the device is not a normal recovery step. On dual-SIM phones, verify the sending SIM.
3. Separate carrier problems from platform problems
Check airtime/bundle, coverage and the recipient number. Try one ordinary SMS directly from the gateway phone to a number you are authorised to test. If that fails too, address the SIM/carrier issue first. A sent status without a delivery report does not prove receipt or failure.
4. Reconcile before trying again
Inspect message and processing attempts before resending. For API requests, reuse the original idempotency key and payload after a recoverable timeout. Do not use a fresh key to repeat an uncertain send. If a campaign recipient is in dead-letter handling, resolve the cause before using its bounded retry option; do not assume exactly-once mobile-network delivery.