Common Issues

Connection issues

Gemini CLI can't see my data after the flow runs successfully

This usually means the Coupler.io connector isn't active or properly configured in your Gemini CLI session. Check the following:

• Confirm that the Coupler.io connector is set up and enabled in your Gemini CLI configuration.
• Start a new Gemini CLI session after confirming the connection — an existing session may not pick up a newly activated connector.

If the connector is active but Gemini CLI still can't access the data, try removing and re-adding the connector configuration.

MCP connector timeouts or data fetch gets stuck

Intermittent timeouts when Gemini CLI calls the data connector are a known issue with MCP-based integrations. This can happen when datasets are large or the connection experiences latency.

If you're hitting this frequently, try reducing the amount of data sent to Gemini CLI by filtering at the source level in Coupler.io. Sending a focused, smaller dataset is more reliable than sending everything.

If the problem persists across multiple sessions, contact Coupler.io support — this may require investigation by the engineering team.

Data issues

Gemini CLI sees fewer rows than the Coupler.io preview shows

A mismatch between the Preview in Coupler.io and the data Gemini CLI receives can occur when the same identifier (for example, an ad_id) appears multiple times, and deduplication logic affects the export differently than the preview.

Don't rely on the Preview tab alone to confirm what Gemini CLI will receive. Always verify the actual row count in Gemini CLI after running the flow. You can also configure a Google Sheets export to verify that the number of rows is the same and to check what's missing.

If you notice specific rows are missing, note the relevant IDs and contact Coupler.io support with the data flow details — this type of discrepancy requires engineering investigation.

Permission errors

"You've reached your destination limit" or AI usage is restricted

Coupler.io plans have limits on destination type. If you're using Gemini CLI as a destination and also sending data elsewhere (for example, Google Sheets), you may hit this limit.

To resolve this, either:

• Remove the other destination and use only Gemini CLI, or
• Upgrade to a higher Coupler.io plan that supports multiple destination types.

Each active data flow counts toward your plan limits. If you created a test flow with a different destination, delete it to free up your destination slot or upgrade to a higher plan.