Refresh issue with Gen1 dataflows linked to Gen2 dataflows

Hi mathsab 

The issue you’re facing with Gen1 dataflows failing to refresh when linked to Gen2 dataflows—despite the Gen2 dataflows themselves refreshing successfully—is a known compatibility and reliability problem that arises from the architectural differences between Power BI Dataflows Gen1 (running on the legacy Power BI engine) and Gen2 (running on the new Fabric Dataflow engine). The error message “Expression.Error: The key didn’t match any rows in the table” typically indicates that the Gen1 dataflow is attempting to access an entity or field in the Gen2 dataflow that is momentarily unavailable, renamed, or temporarily locked during refresh or caching. Since your Gen2 dataflows refresh consistently and the SQL structure remains stable, the issue is most likely due to intermittent connectivity or synchronization failures between the Gen1 and Gen2 environments, especially given that they’re in different licensing capacities (Fabric vs. PPU). To mitigate this, you can try re-establishing the dataflow link by clearing the cached connections and reconnecting via the PowerPlatform.Dataflows connector, or exporting and recreating the Gen1 dataflows as Gen2 dataflows within the same Fabric workspace to ensure consistent refresh orchestration. Alternatively, staggering refresh schedules further apart or introducing a short buffer delay between the Gen2 and Gen1 refreshes can sometimes stabilize the dependency chain.