Open jhult opened 2 months ago
Is this a workaround for something broken?
The issue title describes a solution. An alternative title might say "Repeated API calls return 500" or some other symptom. I can't tell the error code from the screenshot, but if we update the title to include the symptom, we might better be able to address the root problem. Perhaps the API call is broken and we can simply fix it.
I will correct the title.
API calls occur regularly without regard for whether the prior API call has returned. No timeout handling occurs. Even if a prior API call were to return, results would then be pending on a subsequent API call which has not yet returned. Server becomes loaded with API calls that are not even used.
I see. I tried reproducing this the other day and couldn't. Could you add some details on what page/where the problem manifest? The code for polling is located in multiple places and I'm not sure the solution is trivial enough to fix them all.
Ok a closer look at the image provided shows that some calls are taking several minutes. Thanks for the elaboration.
I'm not sure what the solution is for this issue. It seems like we need a workaround until API endpoints are more performant. Should we disable polling until this is not an issue?
Just check to make sure that the prior call has returned before invoking another.
I don't think this is an pressing issue right. It is going to the bottom of the backlog.