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
If you're having issues with threads outliving your request, check [Background threads and synchronous mode](#background-threads-and-synchronous-mode)
538
538
539
-
## Troubleshooting
540
-
541
-
### Request size limits
542
-
543
-
{% include content/tracking-api-limit.md %}
544
-
545
-
546
-
{% include content/troubleshooting-intro.md %}
547
-
{% include content/troubleshooting-server-debugger.md %}
548
-
{% include content/troubleshooting-server-integration.md %}
549
-
550
-
### Override context value
551
-
552
-
In some cases, you will want to manually pass in `ip` or `userAgent` values. Since Segment does not automatically send these, you can pass these through the `context` object as follows:
Be sure to see the full [reference of supported keys](/docs/connections/spec/common/#context).
562
-
563
-
### OAuth 2.0
539
+
## OAuth 2.0
564
540
565
541
Enable [OAuth 2.0](/docs/connections/oauth/) in your Segment workspace to guarantee authorized communication between your server environment and Segment's Tracking API. To support the non-interactive server environment, the OAuth workflow used is a signed client assertion JWT.
{% include content/troubleshooting-server-debugger.md %}
582
+
{% include content/troubleshooting-server-integration.md %}
583
+
584
+
### Override context value
585
+
586
+
In some cases, you will want to manually pass in `ip` or `userAgent` values. Since Segment does not automatically send these, you can pass these through the `context` object as follows:
0 commit comments