Forum Discussion

ray_codex's avatar
ray_codex
Icon for Resolver II rankResolver II
1 year ago
Solved

No Pipeline output

Hi,

 

I just switched from trail to F4 capacity. I tried running a pipeline today, but the output is missing:

I dont have a clue why this occurs. Anyone who encountered this? Pipeline seems to be running, because the cancel button is active and I can see it in my notifications.

  • Hi ray_codex ,

     

     

    Thanks for sharing this! This issue might be related to how Fabric handles capacity transitions, especially when moving from a trial to a paid SKU like F4.

    Here are a few things you can check:

    1. Pipeline Output Location
      Sometimes after switching capacities, the default output location or linked services might get misconfigured. Double-check the destination settings in your pipeline activities.

    2. Permissions & Workspace Binding
      Ensure that your workspace is correctly bound to the new F4 capacity and that your user has the necessary permissions to write outputs.

    3. Capacity Activation Delay
      After switching to F4, there might be a short delay before the capacity is fully active. Try restarting the pipeline after a few minutes.

    4. Monitor Tab & Logs
      Go to the Monitor tab in Fabric and check the activity run logs. Even if the output is missing, the logs might show whether the pipeline completed successfully or failed silently.

    5. Known Issues
      There have been a few reports of similar behavior when switching capacities. If this persists, it might be worth raising a support ticket or checking the Fabric Known Issues page.

    Let us know what you find — happy to help troubleshoot further!

     

2 Replies

  • Hi ray_codex ,

     

     

    Thanks for sharing this! This issue might be related to how Fabric handles capacity transitions, especially when moving from a trial to a paid SKU like F4.

    Here are a few things you can check:

    1. Pipeline Output Location
      Sometimes after switching capacities, the default output location or linked services might get misconfigured. Double-check the destination settings in your pipeline activities.

    2. Permissions & Workspace Binding
      Ensure that your workspace is correctly bound to the new F4 capacity and that your user has the necessary permissions to write outputs.

    3. Capacity Activation Delay
      After switching to F4, there might be a short delay before the capacity is fully active. Try restarting the pipeline after a few minutes.

    4. Monitor Tab & Logs
      Go to the Monitor tab in Fabric and check the activity run logs. Even if the output is missing, the logs might show whether the pipeline completed successfully or failed silently.

    5. Known Issues
      There have been a few reports of similar behavior when switching capacities. If this persists, it might be worth raising a support ticket or checking the Fabric Known Issues page.

    Let us know what you find — happy to help troubleshoot further!

     

  • Thank you! It had to do with throtteling, I'm looking into it now.