Fix a publish that only partly finished | Baker Help Center

Fix a publish that only partly finished

  • Updated
  • 3 min read
  • Every plan
  • Who can do this: admins and members

In short

A publish has two steps: your pages go live first, then each ad and tracking change is applied on its platform. A platform can refuse one change, for example a budget below its minimum, while everything else lands. The chat then says "Published, but one change didn't go through." Press Fix this: the chat reopens with the failures written into your message box, and Baker prepares a corrected change for you to publish.

By the end, you can read a partly finished publish and get the missing changes live.

Publish looks like one action, but it is two. First your pages go live. Only then does Baker apply each ad and tracking change on its platform, one by one, because an ad must never point at a page that is not live yet. Each platform answers each change on its own, so one can say no while the rest say yes.

What do I see when part of a publish failed?

The publish notice in the conversation turns red and reads Published, but one change didn’t go through. (or how many). Below it:

  • Each platform with a failure, and how many of its changes did not land, for example Meta Ads, 1 of 6.
  • Each change that did not go through, named as Baker described it when it prepared it.
  • A reassurance that everything else is live and nothing is lost.

The pill beside the chat’s name reads Partly published instead of Completed. Inside each platform’s tab in the changes panel, the same failure shows how many changes landed and which did not.

How do I fix it?

  1. Press Fix this on the publish notice.
  2. The chat reopens, and your message box fills with a request listing each failed change and the platform’s own reason for refusing it.
  3. Add anything you want Baker to know, such as “keep the budget under 50 euros a day”, and send it.
  4. Baker reads the reasons, prepares corrected changes, and lists them on the right like any other change.
  5. Review them and press Publish.

Only the failed changes are sent again, in their corrected form. What already went live stays as it is.

What if a platform is just busy?

Sometimes nothing is wrong with the change: the platform is simply not taking more changes from Baker at that moment. Then the notice is amber, not red, and says the changes are waiting their turn, with roughly when Baker sends them again on its own. You don’t need to do anything.

If you would rather make those changes yourself on the platform, press Don’t send these and confirm. Baker will not send them, now or later. This cannot be undone from the chat; to have Baker make them again, ask in a new chat.

What about a change that failed for a passing reason?

Inside a platform’s tab, a failure that may not repeat (a dropped connection, for example) offers Retry the changes that didn’t go through (for Tag Manager and Google Analytics, Retry the changes that didn’t apply). Only those run again; the ones that landed stay as they are. If a retry fails the same way, use Fix this instead.

When should I ask for help?

If the notice says Published, but your pages haven’t gone live yet., the problem is with your pages, not a platform. Your changes are saved and go out with the next successful publish, and Baker’s team is told. If it lasts, open Requests in the sidebar, or write to support@withbaker.com. See Contact support.

Troubleshooting

If you see "There is no Fix this button."
Wait until no platform is still sending; the list of failures may still grow until then. Fix this only appears on the chat's latest publish, and only for admins and members.
If you see "The notice says changes are "waiting their turn"."
The platform is not taking more changes right now. Baker sends them again on its own at the time shown; there is nothing for you to do.
If you see "The same change fails again after a retry."
The platform refused the change itself, so sending it again gets the same answer. Use Fix this so Baker changes the plan.

Questions

Did the rest of my publish go live?

Yes. Your pages and every change that went through are live. The ones that did not are listed by name and stay saved exactly as they were written.

Why doesn't Baker just send the failed change again?

Most refusals are about the change itself, such as a budget, a limit on an ad set or an ad that can no longer be edited. Sending it again would fail the same way, so the change has to be corrected first.

Can I make the change myself on the platform instead?

Yes, for changes a platform is holding back to send later. Press Don't send these and Baker will not send them; then make them yourself on the platform.

How often does this happen?

Often enough to plan for it. Platforms refuse changes for their own rules, so check the notice after every publish that includes ad changes.

Next steps

Was this helpful?