Hi. Given that a non-blocking flow is run when collection A is updated and we have an update operation in this flow, if I enable emit event this causes an infinite loop. When disabled, the data after update is not emitted which means I do not see the latest data in directus without refreshing and also if I use websocket in another app listening for changes to collection A, I still do not receive any event message after the flow runs. This has been a huge limitation and I cannot find any solution. Changing to blocking flow would require a full rewrite of all the code and would affect the business logic.
Any way to get this implemented so that using websocket at least I can receive the event message after the update operation runs in the flow with emit event disabled to prevent the infinite loop? TIA.