Save the original reference
Record the message link, order ID and current status before a planned deletion. If the message has already disappeared, keep whatever purchase record remains. A channel URL or screenshot of replacement text does not necessarily identify the original requested target.
Ask about the unfinished scope
Review the selected service's conditions for unavailable content and contact support with the relevant timeline. Do not assume that remaining quantity automatically transfers to a new post. A replacement message may require a separate compatibility check and a distinct order.
Separate the replacement plan
If a new message is published, record its link and purpose as a new campaign item. Confirm the old request's final state before deciding on additional spending. This prevents an unresolved order from being hidden inside a larger combined campaign total.
Decision checklist
| Decision | What to check |
|---|---|
| Original | Message reference and order ID |
| Status | Unfinished or final state |
| Replacement | New target checked separately |
Worked example
Suppose an administrator removes an announcement to correct a major error and republishes it. Even if the wording is similar, the replacement should have its own target record. Ask how the existing request is treated before assuming its unused scope follows the new message.
Example figures explain the decision; they are not current prices or promised results.