For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Postman
PricingEnterprise
Contact SalesSign InSign Up for Free
HomeDocs
HomeDocs
      • Overview
      • Debug with Insights
      • Customize Insights
        • Overview
        • Memory errors
        • Traffic errors
      • Uninstall Insights Agent
      • FAQ
Postman API Platform

Product

  • Postman Overview
  • Enterprise
  • Spec Hub
  • Flows
  • Agent Mode
  • API Catalog
  • Fern
  • Postman CLI
  • Integrations
  • Workspaces
  • Plans and pricing

API Network

  • App Security
  • Artificial Intelligence
  • Communication
  • Data Analytics
  • Database
  • Developer Productivity
  • DevOps
  • Ecommerce
  • eSignature
  • Financial Services
  • Payments
  • Travel

Resources

  • Postman Docs
  • Academy
  • Community
  • Templates
  • Intergalactic
  • Videos
  • MCP Servers

Legal and Security

  • Legal Terms Hub
  • Terms of Service
  • Postman Product Terms
  • Security
  • Website Terms of Use

Company

  • About
  • Careers and culture
  • Contact us
  • Partner program
  • Customer stories
  • Student programs
  • Press and media
Twitter iconLinkedIn iconGithub iconYouTube iconInstagram iconDiscord icon
Download Postman
Privacy Policy

© 2026 Postman, Inc.

Postman InsightsTroubleshoot Insights

Diagnose and troubleshoot Insights errors

||View as Markdown|
Was this page helpful?
Previous

Customize your Postman Insights

Next

ECS memory issues

Built with

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.

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.
  • 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 tab.

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

  • ECS memory issues.
  • API traffic errors.