You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting timeouts while approving a Follow request and it's difficult to parse logs, so I'm not sure if the request is triggering fetches to remote instances and failing or some requests are happening at the same time.
I set the timeout to 1s to avoid crashing the CMS but this seems to low for current requests (but too high for B2B connections?)
The text was updated successfully, but these errors were encountered:
we discussed replying the request with a collection of requests statuses but i'm not sure now if i opened an issue about this, so i'm leaving this comment to not forget again
We should probably return instantly to the outbox request, and queue the requests to other instances (with p-queue). Maybe also set the amount to do parallel with something like p-map. Or ideally a queue that persists to disk (to also retry on failed.)
I'm getting timeouts while approving a Follow request and it's difficult to parse logs, so I'm not sure if the request is triggering fetches to remote instances and failing or some requests are happening at the same time.
I set the timeout to 1s to avoid crashing the CMS but this seems to low for current requests (but too high for B2B connections?)
The text was updated successfully, but these errors were encountered: