Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric certified for FREE! Don't miss your chance! Learn more
Our data ingest pipelines use a connection to a general pipeline for all data sources. Originally imported the workspaceID from a variable in the parameter set which was then set as a library variable. In December we changed this to to use the workspaceID from the DataFactory.
Since then this warning has been shown on the library variable tab:
This did not result in any errors since implementation in December until last night when all pipelines in production failed and now all workspaces give the same error:
Has there been a recent update which changes this from a warning to an error?
Hello @MilanPit
Check if you have a Variable Library item in your workspace called "Parameters" and a Variable called "WorkspaceID". It is quite likely that you have either one or both missing. If they are both there, then you can try deleting the variable reference from the list and re-binding it again with the Variable Library.
Also, when you're referencing the variable library, you'd need to refer it using the correct name - your library variable is called WorkspaceID (Name of the variable) but you're referencing a variable called GenericPipeline. GenericPipeline should exist in the variable library list of your pipeline.
Hi @MilanPit
Thank you for reaching out to the Microsoft Fabric community forum.
The failure occurs because the pipeline still contains a reference to a library variable named WorkspaceID, even though that variable no longer exists in the associated Parameters library. When the Workspace ID was moved to @pipeline().DataFactory, the old library‑variable reference remained in the configuration, and Fabric attempts to resolve all referenced variables during execution. If any referenced variable is missing, the pipeline cannot complete the resolution step and returns a VariableNotFound error. Removing the outdated WorkspaceID library reference from Settings → Library variables, or recreating the variable in the library if it is still needed, will ensure the pipeline runs successfully.
For more details, please refer to the Microsoft official documentation on
Troubleshoot Variable Libraries - Microsoft Fabric | Microsoft Learn
Get Started with Variable Libraries - Microsoft Fabric | Microsoft Learn
If you have any further questions, feel free to reach out and we'll be glad to assist.
Regards,
Microsoft Fabric Community Support Team.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Fabric update to learn about new features.
| User | Count |
|---|---|
| 24 | |
| 6 | |
| 5 | |
| 3 | |
| 2 |
| User | Count |
|---|---|
| 58 | |
| 11 | |
| 10 | |
| 8 | |
| 7 |