# Diagnose and troubleshoot Insights errors

Postman Insights shows you the properties of your system based on real-time API traffic. For Insights to work, the Insights Agent needs to see your API traffic. As you work in Insights, you may encounter errors and receive error messages. In many of these cases, there's a solution.

The Insights Agent doesn't support these three cases:

* Encrypted traffic.
* gRPC/GraphQL.
* PaaS platforms where the Insights Agent can't easily access the network traffic through packet capture. Known platforms in this category are Heroku and Render.

If you experience any of these cases, contact [Support](mailto:observability-support@postman.com).

Postman provides more information about how to debug what's going on:

* Diagnostic information in the CLI itself. If your traffic is getting blocked in a way that the Insights Agent recognizes, your CLI shows error output describing what's gone wrong. If you need help resolving your issues, email your log output to [Support](mailto:observability-support@postman.com).
* Information about encrypted traffic and errors in Postman. To see if your agent is working, or to debug problems, you can see traffic error states and messages in the Insights Project's [**Diagnostics**](/docs/insights/reference/app/diagnostics-tab/) tab.

The following are some common issues you may experience and their respective solutions:

* [ECS memory issues](/docs/insights/troubleshoot/memory/).
* [API traffic errors](/docs/insights/troubleshoot/traffic/).