Troubleshooting & FAQ

Practical resolutions for common technical errors encountered during CSV ingestion, Google Ads OAuth synchronization, and Model Context Protocol handshakes.

Last updated: October 2026

This troubleshooting guide addresses the most frequent errors encountered when setting up workspaces, parsing ad exports, and connecting AI agent tools.

CSV Ingestion & Pre-Flight Errors

“Dataset must contain at least 90 distinct days of historical data”

Cause: You exported campaign totals without selecting daily breakdown, or selected a date range shorter than 3 months.

Fix: In Meta Ads Manager, ensure you click Breakdown → Time → By Day. In Google Ads, click Segment → Time → Day. Select a date range of 90 to 365 days ending yesterday.

“Unrecognized date column format”

Cause:Export contains text headers like “Reporting Period: Oct 1 - Oct 15” in the first line, shifting table headers down.

Fix: When exporting from Meta Ads Manager, select Export table data rather than full report summary. PaceCast automatically trims metadata preambles if the header row contains recognizable column names.

Google Ads Connection Failures

Status: reauth_required

Cause:The user changed their Google account password, revoked access in Google Security settings, or Google's 6-month idle refresh token policy expired.

Fix: In the dashboard, open Workspace Settings → Integrations, click Reconnect Google Ads, and complete the consent flow again. Existing historical sync data is preserved.

“Cannot sync unlinked account”

Cause: Google account was authorized, but the specific 10-digit Customer ID was never selected and linked.

Fix: Complete the second step of the integration wizard by selecting the active operating ad account from the dropdown list.

MCP Connection & Tool Errors

HTTP 401 Unauthorized: “Token expired”

Cause: MCP Bearer JWT tokens have a 3600-second (1 hour) expiration lifetime.

Fix: Ensure your MCP client implements standard OAuth token refresh, or generate a long-lived enterprise token if running persistent background sidecars.

“Workspace not found or unauthorized”

Cause: The client_id supplied in the tool arguments does not belong to the user associated with the Bearer JWT.

Fix: First invoke list_clients to discover all workspace UUIDs accessible to the authenticated identity.

Interpreting Validation & Volatility Flags