You need a quarterly integration report. Gathering traffic charts, retries and errors by hand takes time. EchoRelay can produce a project usage report as a PDF, ready to bring to the review.
The report gives an operational overview: request volume, outbound deliveries, retries and error summaries. It helps a manager and an engineer discuss the same period with the same evidence.
Download the period you want to discuss
Open Usage report in the project, choose From and To, then select Download PDF. Usage reports are available on paid plans. The usage-report guide explains access and the available periods.
A custom period is adjusted to whole weeks, and the week still in progress is excluded. Read the period printed on the report before sharing it. Dates through today still exclude the unfinished week.
For a finished calendar year, use Annual report and Download year. The current year's report becomes available after the year has closed. The page states the allowed span for a custom report.
Use the summary to choose the next question
Suppose the report shows more retries during the period. That is a reason to investigate, not an explanation by itself. The error summary can help you decide whether to start with target failures, request problems or another category.
Request volume and outbound delivery volume answer different questions. One incoming request can be sent to several targets, so they need not rise together. Keep that distinction when discussing growth or a new integration route.
The report also groups retry attempts and shows common errors and busy paths. Use those summaries to pick the next question: did more traffic arrive, did the delivery pattern change, or did a particular target begin refusing requests?
Then use delivery receipts to investigate individual requests. A period report cannot tell you whether a particular order was accepted, and it does not prove that the partner completed its business process.
Keep reporting separate from live troubleshooting
The PDF is downloaded from the panel. There is no report-generation API or MCP tool in this workflow, so this download cannot be automated through those interfaces.
If usage data is temporarily unavailable, the download reports that problem instead of producing a PDF full of zeroes. Try the report again once the data can be read.
Bring the PDF to the review. Keep the delivery receipts for requests that need a closer look.
