Common Issues

Connection issues

404 Not Found — "Web.Contents failed to get contents"

This is the most common issue when setting up Power BI for the first time. The integration URL only becomes active after your Coupler.io data flow has completed at least one successful run.

Fix:

1. Go back to your data flow in Coupler.io

2. Click Run now and wait for it to finish

3. Return to Power BI and try the URL again

Do not paste the integration URL into Power BI before running the data flow. The URL will return a 404 error until data has been exported at least once.

Integration URL is greyed out and cannot be copied

The Generate link button may appear greyed out if the data flow hasn't been run yet, or if a required field in the destination configuration is incomplete.

Fix: Make sure your data flow has been saved and run at least once successfully. If the button is still greyed out, check that all required destination fields are filled in before saving.

Integration URL stops working after a period of inactivity

If your data flow has not run in more than 60 days, the integration URL will be deactivated automatically.

Fix: Run the data flow manually in Coupler.io to reactivate the URL. Then refresh your Power BI report to restore the connection.

Set up a recurring schedule in Coupler.io to prevent inactivity deactivation — even a low-frequency schedule (e.g., weekly) will keep the URL active.

Power BI asks for credentials — which authentication method to choose?

When connecting via the Get Data → Web flow in Power BI Desktop, you'll be prompted to choose an authentication method. Always select Anonymous — the integration URL contains an access token that handles authentication.

Data issues

New columns added to the source don't appear in Power BI after refresh

Power BI caches the column schema from the first import. If you add new metrics or dimensions in Coupler.io after the initial setup, those columns won't automatically appear in your report.

Fix:

1. In Power BI Desktop, open the Query Editor

2. Find and click the gear icon next to the Expanded Column1 step (or similarly named expansion step)

3. Check the list for your missing columns and select them — avoid using the search box as it can deselect other fields

4. Click OK, then go to File → Close & Apply

Data in Power BI doesn't match what I see in the source

Discrepancies between your source (e.g., GA4, Airtable) and what appears in Power BI can happen for a few reasons:

• Sampling — some APIs (like GA4) return sampled data for large date ranges

• Date range mismatch — the data flow may be pulling a different date range than you're comparing against

• Blank fields — some source fields are only populated for certain record types and will appear empty for others

Fix: Check your data flow's date range settings and compare the preview data in Coupler.io against the source directly. If the Coupler.io preview matches the source, the issue is likely in the Power BI refresh or schema configuration.

Power BI dashboard doesn't update even though Coupler.io ran successfully

Coupler.io and Power BI refresh schedules are independent. Coupler.io updates the data at the URL; Power BI must separately be told to refresh from that URL.

Fix: After each Coupler.io run, manually refresh in Power BI (Desktop: click Refresh; Online: go to the semantic model and select Refresh now). For automatic updates, schedule a Power BI refresh after your Coupler.io run is expected to complete — add at least 10–30 minutes buffer depending on your source volume.

Permission errors

Cannot connect Power BI destination from the Destinations section

Power BI must be configured inside a data flow, not from the standalone Destinations section in Coupler.io. The integration URL is flow-specific and is only generated during data flow setup.

Go to your data flow, navigate to the Destination step, and select Power BI there to generate your integration URL.