How to fix a push to WordPress that failed

When you press Push in the WordPress panel and the post doesn’t update, the panel is telling you why in one of a few specific ways. Work through them in the order below.

The Push button is disabled because of unresolved suggestions

If the document has pending suggested edits, the panel shows a warning below the Push button and the button itself won’t respond. Hovering it explains that the suggestions need resolving before pushing.

• Open the suggestions and accept or reject each one.
• 

This block exists because the editor’s markup would otherwise ship the suggestion styling, both the struck-through original and the proposed replacement, straight onto the live post.

A dialog titled “Before you push…” appears

This means the push was stopped on purpose, before anything was sent to WordPress. It can show one or both of the following, and each has a different fix.

“This post was changed in WordPress since your last sync”

Someone (or something) edited the post directly on the WordPress site after your last pull or push. Pushing now would overwrite that edit, so Workover asks first. You have two choices in the dialog:

• Pull latest from WordPress first — this rewrites the document from the current WordPress content and discards any un-pushed changes here. Review what changed, then push your own edits again if they still apply.
• Overwrite anyway — pushes your version regardless, replacing whatever changed on WordPress. Use this only when you’re sure the WordPress-side edit doesn’t matter (for example, it only touched a timestamp or a field you don’t care about).

You can also spot this coming before you even try to push: the sync status above the Push button reads “New changes in WordPress” with a note showing when it was edited on WordPress and when you last synced.

“Pushing would remove content that exists on WordPress”

The dialog lists specifically what would be lost, such as a number of embedded videos, that exists on the live post but isn’t something the editor here can represent. Pushing would delete it. This time there’s no pull option in the dialog, only:

• Overwrite anyway — pushes and removes that content from the post.
• Cancel — backs out without changing anything.

If that content matters, don’t overwrite. Make the change directly on WordPress instead, or reconsider whether the edit you’re pushing needs to happen at all right now.

Push spins, then nothing happens: no dialog, no confirmation

A successful push shows a brief confirmation that your edits are now live and the sync status flips to “Up to date with WordPress.” If neither of those appears, and there’s no “Before you push…” dialog either, the push failed for a reason the panel doesn’t display a message for. Check, in order:

• The connection to WordPress. Workover pushes using the WordPress account and application password stored for that site. If that password was changed or revoked on the WordPress side, the push can’t authenticate. Reconnect the site and try again.
• The linked post still exists. Push updates a post this document is already linked to. If that post was deleted on WordPress, there’s nothing left to update.
• What that WordPress account is allowed to do. The push acts as that account, so it can only do on the post what that account could do by logging into WordPress directly. If it isn’t allowed to edit or publish this post, the push has nothing to succeed with.
• Whether WordPress is reachable at all. If the site is down, moved, or blocking the request somewhere between it and Workover, the push has no response to work with.

Try the push again after checking these. If it still fails silently, try making the same change directly in WordPress: if that fails too, the problem is on the WordPress side rather than in Workover.