If your Power BI dashboard is connected to Flowsite but data appears later than expected, this article explains why delays occur and how to reduce them.
What's happening
Data submitted in Dashpivot is not appearing in Power BI immediately, or there is a noticeable lag between form submission and the data being visible in the dashboard.
Why this happens
The flow is set to a scheduled trigger (e.g. daily or every 4 hours) — data only updates when the flow runs
The flow has not been manually triggered after new data was submitted
A large number of forms in the template is slowing down CSV generation and load time
Multiple flows are running at the same time, creating concurrent load on the data pipeline
Power BI Online Dataflows are not supported — only Power BI Desktop with Power Query is supported for Flowsite integrations
How to fix it
1. Trigger the flow manually for immediate data
In Flowsite, open the flow and click Trigger flow manually. Once the run completes, refresh Power BI to pull the latest data. This is the fastest way to get up-to-date data without waiting for the next scheduled run.
2. Review your trigger frequency
In Flowsite, open the flow settings and check the scheduled trigger interval. If daily updates are not frequent enough, consider switching to a shorter interval (4 hours or 1 hour) depending on your plan. Note that 1-hour triggers require a Premium or Platinum plan.
3. Reduce the number of active forms
If the connected template has a large number of active forms, CSV generation will take longer. In Dashpivot, archive older or completed forms to reduce the export size and improve refresh speed.
4. Stagger flow triggers
If multiple flows are triggering at the same time, stagger their schedules in Flowsite to avoid concurrent load. This can reduce overall refresh latency across all connected dashboards.
5. Check Power BI Online is not being used
Flowsite integrations are only supported via Power BI Desktop using Power Query. Power BI Online Dataflows are not supported and will not sync data from Flowsite.
If the issue continues
If delays persist after triggering manually and the run shows as completed in Flowsite, contact your Solutions Engineer with the flow URL and workspace details so they can check CSV generation times and run performance.