Refresh Dataflow failed with status: NotFound

Hi samkikibaker ,

We’ve hit this exact “Refresh Dataflow failed with status: NotFound” error before, and even though the message suggests the dataflow doesn’t exist, the problem was actually somewhere else. In our case, the pipeline was calling the dataflow before the dataflow reference was fully published or synced inside the workspace. Even though the dataflow existed visually, Fabric sometimes loses the internal reference after edits, renames, or when parameters are added.

What finally fixed it for us was simply opening the dataflow, letting it load completely, and then hitting save/publish again — but the key difference was that we did this after switching into the exact environment the pipeline runs in. Once the dataflow was re-published inside that workspace context, the pipeline was able to find it again.

Another thing we noticed is that if the dataflow is parametrized, even a small mismatch like a space, casing difference, or an older cached version can cause Fabric to say “NotFound”, even if the name is correct. When we re-published the dataflow and then re-opened the pipeline once, the pipeline started picking up the correct reference.

It’s definitely not a permissions issue or a location issue — it’s more of a “Fabric hasn’t refreshed the internal link to this dataflow” type of scenario. After re-saving the dataflow and letting the workspace update, our pipeline refresh calls worked fine again.

If you’ve already opened and saved it once, try doing it one more time, but make sure you’re in the exact workspace/environment the pipeline runs in. That usually forces Fabric to rebuild the reference and clears the NotFound error.

Hope this helps — happy to share more if you want to compare setups.

Gopi Krishna