Frequent 499 Errors When Sending Client Activities to Jitsu-Ingest
I am experiencing frequent 499 HTTP errors when sending client activities to the jitsu-ingest service. This issue seems to occur intermittently and appears to be related to client-side disconnections before the request is fully processed.
Could you provide guidance on how to mitigate these 499 errors? Specifically, we are looking for advice on:
-
Adjustments to client-side settings that might help reduce these errors.
-
Any recommended configurations or optimizations on the jitsu-ingest side to handle such situations more gracefully.
Thank you for your assistance.
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.