It looks to me that during the action, your session expires, but since the system is still busy it fails to remove the session.
Since the session is connected to your user, it seems that you loose the rights of your user, and that way entity access for the administrator is no longer valid.
Perhaps increasing the session lifetime might solve this issue.
It could also be this bug that has been fixed in Mx8.12:
We fixed an issue that caused session keep alive
to become defunct if a database connection became stale. (Ticket 102373)
Because imho yoiur session should not be destroyed since the microflow is still active.
So you might want to test if the same behaviour occurs in Mx8.12.
Regards,
Ronald
I think David is correct, the session is timing out before the microflow completes.
A solution would be to move the microflow to the background using something like the ProcessQueue or Queue modules. The long running microflow would then run in the background while quickly returning control back to the user. You would need to save the results of the microflow to storage when complete, and have the front end poll to check if this exists. If it does, then they can download it. Alternatively, email a link to download it when it’s completed.
Hope this helps.
As I was checking the live logs in our application, I saw the same error “UpdateConflictException” for a delete action in our application running 8.12.5. Is the issue still occurring Taiga?
How are you exporting more than 1000 records? I am using Datagrid 1 and using the Export to Excel button. it is not allowing me to export more than 1000 records.
I tried using Export to CSV. it allows me to download but it doesn't come in proper format.