You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using custom document actions to extend the publish action, sometimes the document is not published.
It doesn't happen in a specific pattern, but more at random. Looking in the network tab, the POST publish call is not sent when this happens. When it manages to publish, the POST is sent. There is no error in the console.
I came to report the exact same issue. I have a more or less identical custom action as the above.
Some consistent patterns I have noticed:
In my document I have an array of images that seem to be central:
If I don't add anything to the image array the document will be almost always published immediately.
If I add more than two images to the array there's a ~100% change of the document NOT getting published. It will be stuck in the publishing state forever.
When the document is stuck in the publishingstate, I can click Add item to the image array and the document will suddenly be published.
For the the network tab, I can see that in step 2 above, there is no POST to the data/actions/
endpoint, which is is the case in step 1.
Describe the bug
When using custom document actions to extend the publish action, sometimes the document is not published.
It doesn't happen in a specific pattern, but more at random. Looking in the network tab, the
POST
publish call is not sent when this happens. When it manages to publish, thePOST
is sent. There is no error in the console.To Reproduce
Steps to reproduce the behavior:
sanity.config.ts
Screenshots
publish-sanity-bug.mov
Which versions of Sanity are you using?
What operating system are you using?
MacOS. Also experiencing this on our deployed studio
Which versions of Node.js / npm are you running?
❯ npm -v && node -v 10.7.0 v22.2.0
Additional context
I have tried the different examples in custom document actions with no luck.
The text was updated successfully, but these errors were encountered: