Silent fail intermittently while trying to save and publish documents

We are developing a new large site currently on Umbraco 17.4.0 and are seeing a troubling issue we cannot recreate.

I wonder if someone else has either experienced this or could make a guess as to what the issue is?

The problem is when hitting “Save & Publish”, there is neither a green checkbox on the save button nor the “toast” that usually appears when successfully saving/publishing.
Instead nothing happens.

This is very bad for the client’s editors since by this time they have made important changes they cannot save. The only way to continue is to throw away your changes by fully refreshing the window. This always fixes the problem - you can save once again! But your changes are lost.

I’ve seen this on local dev environment and on Azure-hosted environments. I’ve looked at the network requests as well and see where things “stop”.

During regular successful behavior the request flow goes like this:

  • Editor hits Save and publish
  • Backoffice UI makes a PUT network request to /umbraco/management/api/v1.1/document/ba414fb0-xxxx-4f4f-b868-5fb77a40b300/validate
  • Another PUT request is made to /umbraco/management/api/v1/document/ba414fb0-xxxx-4f4f-b868-5fb77a40b300

But when it’s not working, that second PUT request that actually saves the content is never initiated. It makes the validate request, and receives a 200 OK response even. But it never goes to the next step of saving.

No js console logs either when this happens.

Any advice or wild guesses are greatly appreciated!

1 Like

New info has appeared:

When we are in this broken state of not being able to save and publish it is still possible to SAVE successfully. When doing so, it does the validate PUT request first then the saving PUT request sequentially and working.

Hi @karlmacklin

When you say you can recreate it, can you recreate it on a blank Umbraco install? Have you got any packages installed that may be affecting Save and Publish? That’s quite a fundamental issue, so if it is a problem I would have expected more people to be affected and an issue raised.

Does it happen immediately for a user or only after a certain period of time or on certain content?

Could it be a user has been logged off after a certain amount of activity?

Do you have any errors in the Umbraco log?

Justin

No, we can’t sadly recreate it reliably.
No errors in either javascript console log or from the Umbraco runtime.

Only packages are uSync and Skybrud Redirects. More testing will be needed to find this on our end.