Approved ad change went stale? Why it is refused and how to redo it

What it does

Any change prepared ahead of time is based on a snapshot. You looked at the campaign at 10:00, saw a daily budget of 50 and proposed 70. If the client raised it to 80 in Google Ads at 10:20, applying your plan at 10:40 would actually cut the budget, the opposite of what everyone wanted. Statuses behave the same way: a campaign the client paused because the vacancy was filled can be switched back on by an old proposal. Engineers call this a lost update. In ad accounts it is costly, because it changes spend and delivery, and usually nobody notices until the next report.

The manual cure is a habit. Right before applying any change prepared earlier, compare the current value with the value your plan was based on. If they differ, stop and find out why. Check the account change history for who changed it and with which tool, ask the client or the teammate, and decide again on the new numbers instead of repeating the old instruction. Keep plans short-lived, write the starting value next to each planned change and agree who owns which account. A plan that is several hours old is a draft, not an order.

AdAce Ads builds this check into every write. Each proposal stores the state it was made from, such as the budget value and the campaign version. When the proposal is approved and queued, the service compares that snapshot with what it knows now, and the isolated executor reads the live object again right before writing. If something moved, the change is refused with a plain explanation: “the budget was 50 USD, now 80 USD”, “other changes to this campaign ran after the proposal: 2”, or “the campaign data was refreshed from the account: its status or settings changed in the account itself”.

Next to the message there is “Create the same again”. It creates a new proposal with the same kind of change, the same new values and the same reason, but with the campaign's current state as the starting point. The new proposal passes every usual check again, including the client's limits and daily budget cap. Then it waits for approval with password and second factor, or is queued at once if the client's policy is auto and the change qualifies. The old proposal is not edited or reused: it stays in the history and simply expires.

Use the button deliberately. Repeating is right when the goal is still valid, for example the campaign still needs a higher budget and only the starting value changed. It is wrong when the newer state already solves the problem or reflects a client decision: if the budget is now 80 and you repeat “set to 70”, you are proposing a cut. Read the reasons first, look at “Changes outside the service” if the edit came from Google Ads or Ads Manager, and only then recreate. A step that was fine from the old value may now exceed a limit and be refused with its own reason.

Why it helps

• Edits made by clients or teammates are never overwritten blindly.
• The refusal names exactly what changed instead of a generic error.
• One click rebuilds the same change on fresh data.
• The new proposal goes through every check and approval again.

How to set it up

1. Open “Approvals” and find the proposal that could not be approved or run.
2. Read the reason: the budget before and now, other changes that ran, or data refreshed from the account.
3. If the edit came from outside, open “Campaigns” → “Changes outside the service” to see who made it and how.
4. Decide whether the same change still makes sense with the current numbers.
5. Press “Create the same again” and review the before and after of the new proposal.
6. Approve it with your password and one-time code and follow the execution on “Operations”.

Good to know