# Common Issues

## Connection issues

<details>

<summary>My Perplexity account isn't connecting or authorizing correctly</summary>

This can happen if the Coupler.io connector or extension hasn't been properly installed in Perplexity. Go back through the connection step and make sure you've completed any in-app authorization steps on the Perplexity side — not just the Coupler.io side.

Try disconnecting and reconnecting your Perplexity account from within the data flow settings. If the issue persists, check whether your Perplexity plan supports third-party connectors.

</details>

## Data issues

<details>

<summary>Perplexity doesn't seem to "see" my data after a successful run</summary>

After a successful Coupler.io run, it may take a short moment for the data to become fully available in your Perplexity session. Try refreshing your Perplexity session or starting a new conversation.

Also, confirm that the dataset name you configured in Coupler.io matches what you're referencing when querying in Perplexity. A naming mismatch can make data hard to locate.

</details>

<details>

<summary>My dataset in Perplexity contains fewer rows than expected</summary>

Check whether your source is applying filters that limit the returned rows. Some sources have default date range filters or row caps. Review your source configuration in Coupler.io and expand the date range or increase the row limit if needed.

</details>

## Permission errors

<details>

<summary>I get a permissions error when trying to save or run the data flow</summary>

Make sure your Coupler.io account has the necessary permissions to create and run data flows. If you're on a team account, your role may restrict which destinations you can configure — ask your workspace admin to verify your permissions.

</details>