What it is
A best-effort delete of the existing compliance record on a Messaging Service, returning the removed identifier or null when there was nothing there. It never throws, because a missing record is the desired end state.
Also called: already exists error · resubmit campaign · stuck on a rejection
See it
How it works
- 1The retry path reads the existing compliance record on the Messaging Service.
- 2If one exists it is deleted using the builder's own account credentials.
- 3The corrected campaign is then filed cleanly.
Why we built it
Documented on the function: 'Twilio allows exactly ONE UsAppToPerson per Messaging Service, so a rejected campaign has to be deleted before a corrected one can be filed — otherwise the retry fails with "already exists" and the tenant is stuck looking at a rejection they can't clear.'
The problem
- A retry after a rejection failed with an 'already exists' error, leaving the account permanently stuck.
Sound familiar?
What you get
A corrected filing goes through on the first attempt.
The clear-out is safe to run when there is nothing to clear.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →