My data is not refreshing in the PBI App. There are no errors and refresh says complete but the updates I made are not showing up.
This can happen if the dataset refreshes, but the report or app isn’t updated. Try these steps:
1. Go to the workspace, open the report, and hit Refresh manually.
2. If you’re using a published app, go back to the workspace and click “Update App” to push the latest changes.
3. Clear your browser cache or check in an incognito window — sometimes it’s just a caching issue.
That usually fixes it. Let me know if it doesn’t!
I have the same issue - even in Desktop I cannot get data from an updated Portfolio to come through into PBI
We’re having the same issue
I suspect the delay may be related to the limitation mentioned in the documentation below.
It states:
Exported data with more than 1,000 tasks refresh every 4 hours.
The first data load retrieves the most up-to-date data.
Subsequent updates occur every 4 hours.
Reloading the dashboard within that 4-hour window will complete successfully, but it will not return the latest data.
This seems to match what I’m experiencing — refresh completes without error, but the dataset remains unchanged for roughly four hours.
Can anyone confirm whether this 4-hour window is a hard system limitation?
And more importantly, why is the refresh interval specifically set to 4 hours? Is this due to API rate limits, backend processing constraints, caching behaviour, or something else?
Any clarification would be appreciated.
Please find the response from Microsoft forum regarding this issue:
Hi @snehaj214
The 4-hour delay is a documented Asana API limitation, not a Power BI or Gateway fault. For datasets exceeding 1,000 tasks, Asana generates a cached export file that only refreshes every 4 hours. Any refresh triggered within this window pulls the same cached data.
To resolve this, you must bypass the native connector:
Direct REST API: Use the Web connector in Power BI to call the Asana API directly. This requires M code for authentication and pagination but retrieves real-time data.
Middleware: Sync data to a SQL database using ETL tools (like Power Automate or Skyvia) and point Power BI there.
Data Partitioning: Reducing the scope to under 1,000 tasks per request avoids the export cache logic.
The native connector prioritizes stability for large datasets; high-frequency refreshes require a custom API approach.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Regards,
Rita Fainshtein | Microsoft MVP