Small notebook activity is very slow

Hi alloowishus ,

If you are looking for ways to extract the workspace name, You can avoid using a notebook altogether by leveraging built-in pipeline context in Fabric. Fabric pipelines expose system variables such as the workspace ID and pipeline name, which can be accessed directly using dynamic expressions like

@pipeline().workspaceId

. While this gives you the workspace ID instantly without any execution overhead, you can easily derive the workspace name by combining it with a simple lookup or mapping (for example, from a small config table). This approach is significantly faster, more reliable, and eliminates the 30–40 second delay caused by spinning up a notebook.

Regards