Rolling back an SMS adapter while orders are still open
The old client starts after a rollback, but that does not prove work has recovered. The newer version may have changed local records or left unfinished tasks. A SimAggregator adapter rollback plan needs to cover existing orders as well as reinstalling a previous package.
Before release, document the data each version reads: identifiers, timestamps, and links to user actions. If the format changes, provide compatible reads or a separate recovery procedure. Do not delete unfamiliar records merely because the old client cannot display them.
Rehearse locally with synthetic orders at important stages. Upgrade, return to the earlier build, and check that operators can see uncertain cases and background work is not started twice. This exercise does not always require live service requests.
Name the person who decides to roll back and define the checks afterward. If only new work has recovered, report that limitation explicitly. Older orders need their own reconciliation; a successfully started process is not evidence of their outcome. Keep the rehearsal results with the release notes so the next operator can repeat the procedure.