Start with the exact workspace, product, run/job ID, timestamp, and error code. Preserve those details before retrying.

Confirm the Authorization: Bearer ... header, that the key is active, and that the connection is using the intended workspace. Create a new key if the secret was truncated or exposed. Never send the key to support.

Open Settings → Billing and check the active workspace plan and capability state. A key inherits workspace access; creating another key does not add an entitlement.

The requested limit is a ceiling. Broaden the event wording, time window, or research lens. Confirm you supplied a root domain for Company Signal Enrichment. Do not remove the source/date requirement to force a result.

Poll the existing job_id or resume the product run. Check any retry-after guidance. Do not resubmit the original inputs unless the terminal error explicitly makes a fresh submission safe.

Remove the old connection, copy the current configuration from Settings → MCP setup, reconnect, and start a new client conversation. Confirm custom MCP connections are allowed by your client or organization.

Include the workspace name, product, UI or API route, timestamp and time zone, run/job ID, error code, and what you expected. Include a screenshot with secrets removed. Never include full API keys or private keyed MCP URLs.