Issue
The source has already been correctly configured and events are correctly flowing downstream, but they are not visible in the source debugger.
Product
Twilio Segment
Environment
Segment Console
Cause
The most common cause is network restrictions blocking the Debugger’s event stream.
Resolution
If you can't see the event data on a correctly configured source, that generally indicates that there is a client-side issue and something specific on your network or device that is blocking the Debugger from loading events.
If there is anything interrupting the network request for "app.segment.com/debugger-stream" on your network or computer, the Debugger will not be able to load events. Follow these steps:
Check for Network or Device Restrictions
- Ensure your network or device is not blocking requests to
app.segment.com/debugger-stream. This is the endpoint the Debugger uses to load events.
- Ensure your network or device is not blocking requests to
Open the Browser Console
- Use your browser’s developer tools (e.g., press Command + Option + J on Mac) to inspect network activity.
- Look for any failed requests to
/debugger-stream. If you see errors or blocked requests, this indicates a network issue.
Try a Different Device or Network
- Access the Segment Debugger from another device or a different network (such as a mobile hotspot) to rule out local restrictions.
Contact Your IT/Security Team
- If you confirm that requests are blocked, ask your IT or security team to allow access to Segment URLs, especially
app.segment.com/debugger-stream.
- If you confirm that requests are blocked, ask your IT or security team to allow access to Segment URLs, especially
Verify the Fix
- Once the URLs are allowed, reload the Debugger tab. You should now see events flowing.
If Still Unresolved
- Double-check your source configuration in Segment to ensure data is being sent correctly.
- If the issue persists, repeat the above steps or reach out for further assistance.