Forum Discussion
Refresh error
Hi RTNL
This pattern (dataflow + semantic model both failing with only a Request ID and no table or partition listed) almost always means the failure happened before any table was actually processed, which points to a connection or authentication break rather than a data or DAX issue. In practice this is usually caused by expired or changed credentials, a revoked service principal, a rotated database password, or a gateway / VNet / firewall change that blocks the dataflow’s connection to the source. Because the engine cannot even open the source, it never gets far enough to identify a table, so everything shows as NA. Re-authenticate the dataflow connection and check gateway or network access — that almost always resolves this exact failure pattern.
Hi RTNL
This pattern (dataflow + semantic model both failing with only a Request ID and no table or partition listed) almost always means the failure happened before any table was actually processed, which points to a connection or authentication break rather than a data or DAX issue. In practice this is usually caused by expired or changed credentials, a revoked service principal, a rotated database password, or a gateway / VNet / firewall change that blocks the dataflow’s connection to the source. Because the engine cannot even open the source, it never gets far enough to identify a table, so everything shows as NA. Re-authenticate the dataflow connection and check gateway or network access — that almost always resolves this exact failure pattern.