Troubleshooting
What to do when a prompt does not return the expected result, plus the known issues the dev team is tracking. If you find a reproducible symptom, please file a report via Support / Feedback with the version number attached — it speeds up fixes considerably.
First, check the basics
Section titled “First, check the basics”1. Is the Picaro connection still valid?
Section titled “1. Is the Picaro connection still valid?”Most connection / auth errors are caused by an expired Picaro connection. Use Connect ad accounts Prompt 1 to check the connection status. If it has expired, use Prompt 2 in the same category to re-connect via your AI agent environment’s Custom Connector.
2. Is the version current?
Section titled “2. Is the version current?”Use Connect ad accounts Prompt 4 to confirm the current version. Reinstall your AI agent environment’s extension to update (when using MCP).
3. Is the account switch correct?
Section titled “3. Is the account switch correct?”When managing multiple clients through an agency, it’s easy to operate on the wrong account by accident. Use Prompt 1 to verify the current default account.
Known issues (work in progress)
Section titled “Known issues (work in progress)”These are the issues the dev team has on record, with current workarounds. Each has a feedback ticket. Items are removed from this list as they ship.
OpenAPI tool registry mismatch
Section titled “OpenAPI tool registry mismatch”Symptom: In the AI-agent environment, “this tool isn’t in the available-tools list” appears. A tool that exists on the MCP server isn’t recognized.
Affected tools (samples):
assign_search_term_labels/assign_product_labels/assign_dsp_labelscheck_budget_statusdiscover_report_sources/collect_report_dataset/build_report_slide_specprecheck_contribution_datapreview_search_term_action_workflow
Workaround: The AI agent will automatically suggest a fallback. It may still work via your AI agent environment’s extension (direct MCP call). The list above will shrink as fixes ship.
detect_negatives / analyze_promotion duplicate-row bug
Section titled “detect_negatives / analyze_promotion duplicate-row bug”Symptom: For negative-keyword candidates and Auto→Manual promotion candidates, the same search term shows up multiple times (up to 3x).
Affected prompts:
- Add negative keywords Prompts 1, 3
- Promote Auto to Manual Prompts 1, 2
- Adjust bids Prompt 3 (zero-sale target carve-out)
Workaround: Duplicates are stripped on execution, so the operational impact is none. The displayed count looks inflated, but item_id-deduplicated, the actual count is correct.
RainForest API (external) outage
Section titled “RainForest API (external) outage”Symptom: Competitor-ASIN auto-labeling fails with “product info fetch failed (HTTP 403)” and returns 0 items.
Affected prompt: Design labels Prompt 1
Workaround: Transient outage on the upstream RainForest API. Re-run after a wait. If reproducible, please file a ticket.
get_dashboard KPI=0 aggregation problem
Section titled “get_dashboard KPI=0 aggregation problem”Symptom: On View KPI dashboards Prompt 1, ad spend / sales / orders return as zero (sales-trend may still show a non-zero value, producing a confusing inconsistency).
Affected prompt: View KPI dashboards Prompt 1
Workaround: This happens with certain combinations of period and frequency. For example, frequency=monthly over a 30-day range can return zero. Re-run with frequency=daily.
placement-table orders=0 aggregation problem
Section titled “placement-table orders=0 aggregation problem”Symptom: When proposing placement-multiplier adjustments, orders comes back as zero for every row, so CVR-based multiplier suggestions cannot be produced.
Affected prompt: Adjust bids Prompt 6
Workaround: An order-data aggregation issue. Lower min_clicks to re-run, or wait for additional data.
Q. I sent the prompt but nothing came back
Section titled “Q. I sent the prompt but nothing came back”The connection may be dropped, or the prompt may not be recognized by the agent.
- Check connection status with Connect ad accounts Prompt 1
- Confirm the version in Support / Feedback
- Restart your AI agent environment’s extension (for MCP connections)
Q. The proposal ID expired
Section titled “Q. The proposal ID expired”Proposals have a 24-hour TTL. Re-run the same optimization prompt with the same conditions to get a fresh proposal ID. Or use extend_proposal to push the TTL up to 48 hours.
Q. KPI targets are registered but the prompts don’t reference them
Section titled “Q. KPI targets are registered but the prompts don’t reference them”KPI targets are auto-referenced for the month they cover. Use Set monthly KPI targets Prompt 2 to confirm the target month is correctly registered.
Q. ASIN labeling returns thin results
Section titled “Q. ASIN labeling returns thin results”Depends on what the upstream RainForest API returns. When working with non-domestic marketplace ASINs (US / EU / UK), run Design labels Prompt 5 first to set update_asin_enrichment with amazon_domain / currency / language.
Q. SQP data won’t load
Section titled “Q. SQP data won’t load”SQP market search funnel only supports products registered in Brand Analytics. With list_sqp_products, only data_crawled items work (not_monitor products cannot be used).
Q. “Won’t be applied until you approve” appears but I want it applied
Section titled “Q. “Won’t be applied until you approve” appears but I want it applied”Immediately after the proposal is generated, reply with “execute” or “approve”. For full application no extra args are needed; for partial application, specify proposal-item IDs. See Set automation rules Prompt 2.
Q. “Amazon Ads OAuth required” shows up
Section titled “Q. “Amazon Ads OAuth required” shows up”Creating new campaigns (Create campaigns) requires the Amazon Ads account link. Data retrieval / analysis / optimization / dashboard view do not require it. Use Connect ad accounts Prompt 3 to authorize.
Please report
Section titled “Please report”If you encounter a symptom not listed here, please file a report via Support / Feedback Prompt 1 so the dev team can investigate. Including the version number (from Connect ad accounts Prompt 4) speeds up the fix.