Case file #02: How Ask Junipeer AI found the cause of a report issue in 3 minutes

Case file #02: How Ask Junipeer AI found the cause of a report issue in 3 minutes

10 Sept 2026
Marta Sakalouskaya
Marketing and Communications

Incident date: 10 September 2026 - Area: Task report download - Rows expected: 3 - Diagnosis: Ask Junipeer AI - Time to root cause: Under 3 minutes - Status: Resolved

Summary

On 10 September 2026, a merchant downloaded the report for a single task and received more rows than the task contained. Ask Junipeer AI, our purpose-built support AI, found the cause within 3 minutes of the issue being shared with it: the task filter wasn't being applied to the download. All the data in the file belonged to the merchant's own integration. The fix was ready the same day and has since been deployed.

What happened

Every task in the Junipeer platform has a report that merchants can download as a CSV file. When this merchant downloaded the report for one task, the file held 9 rows instead of 3: the 3 rows from that task and 6 from earlier runs.

All 9 rows were the merchant's own data. The report included more of it than it should have.

Timeline

  • 10 Sep, 13:28 - Issue shared with Ask Junipeer AI

  • 10 Sep, 13:31 - Cause found

  • 10 Sep - Fix ready

Root cause

When a merchant downloads a task report, the download button sends the task to the report so it can show that task's rows. The report was reading the task from a different field. With no task to filter by, it included every run instead of the one requested.

How Ask Junipeer AI found it

Ask Junipeer AI is built to diagnose integration issues. It works directly with the platform: the logs, the data behind each task, and the code that handles it.

It compared the downloaded file with the platform's logs and traced each of the 9 rows back to its run. Three came from the task, and six from earlier runs. It then read the code behind the report and found that the report was reading the task from a different field than the one the button sends. It also confirmed that every row belonged to the merchant's own integration.

All of this took less than 3 minutes.

The fix

The report now reads the task the button sends. Downloading a task's report returns that task's rows and nothing else.

What this means for merchants

A report with a few extra rows is a small issue. It still deserved a full answer, and it got one without waiting in a queue.

Ask Junipeer AI reads the file, the logs and the code in one pass. That's how our support team had a precise explanation within 3 minutes of the issue being shared, and why no issue is too small to look into.