Persistent Conflict Errors #13491
Description
Describe the bug
On the incidents page in Sentinel, when we try update an incident (assign, set to active or closed, add tags) we get consistent conflict errors. You cannot perform an action without refreshing the page each time. This started occurring after the Sentinel outage last week. It occurs in all of our workspaces that we manage. The conflict errors usually only occur when you try do another step before the first step has successfully updated, but now the conflict errors occur every time you try do another step after the first one you have done.
To Reproduce
Steps to reproduce the behavior:
- Go to 'Sentinel and select your workspace/s and then go to incidents.
- Click on an incident and assign it, wait for it to be assigned properly, then set it to active, closed or add a tag.
- See error
Expected behavior
What usually happens, is you assign it, wait for it to assign successfully, then continue with your successive steps, waiting for them all to complete before performing the next one. The conflict errors usually only occur when you try do another step before the first step has successfully updated, but now the conflict errors occur every time you try do another step after the first one you have done.
You can also use the action tab to perform all these steps in one go, usually this always works, but with these conflict errors, sometimes that doesn't work either.
Screenshots
Desktop (please complete the following information):
This has been observed on multiple different devices but here is one for example.
- OS: Windows
- Browser: Edge
- Version: Version 144.0.3719.82 (Official build) (64-bit)
Additional context
This is quite an important issue for us as the conflict errors cause us to take longer with incidents, increasing our MTTT, MTTA and MTTC.