When attempting to disable workflows from the workflows index page, the state of the workflows doesn’t update despite the successful toast feedback.
1 Like
This appears to be a UI state sync issue rather than a failure of the disable action itself.
The success toast suggests the backend request completes successfully, but the workflows list is not being refreshed or re-fetched afterward. As a result, the UI continues to show the old enabled state until the page is manually refreshed.
In short, the disable operation likely succeeds, but the client state isn’t updating correctly after the bulk action.
We have reproduced. We’ll get it fixed up
1 Like
Hi, we shipped an updated API to fix this issue. Let us know if you continue to see problems.
1 Like