Due to excessive logic in the API and its slow performance, I have resorted to handling some of the logic with @OnEvent.
The problem arises when the frontend runs the @GET API immediately after this API, potentially without waiting for @OnEvent to update. As a result, users may see inconsistent data.
How can these issues be addressed? Users often complain about the API's speed when it is slow, and discrepancies arise when @onEvent is involved...
I am considering approaching the frontend team to possibly delay the execution of the @GET API....