Forum Discussion
Asana Data Not Updating for ~4 Hours After Refresh (API / Gateway)
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
Super UserHi 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