Forum Discussion

savvyt's avatar
savvyt
Frequent Visitor
1 year ago
Solved

notebookutils.notebook.runMultiple no longer display the execution results table

Hi everyone,

Thanks in advance! We noticed that starting yesterday, our notebookutils.notebook.runMultiple executions no longer display the execution results table when ran from pipeline (edit 12. june 2025, execution results table still shows only when the notebook is ran manually).

Before:

 

Now, whether the run is successful or fails, triggered manually or scheduled via pipeline, we now just see a blank row where the execution info used to be.

Current:

 

Has anyone else experienced this or know if there’s been a recent change affecting this behavior?

Appreciate any insights!

8 Replies

  • Hi savvyt, I just tested this myself, but I still get the activity progress table on Fabric service version 13.0.26056.36. You may want to check you DAG configuration for errors, although you might expect the function to through an error.

     

     

    • savvyt's avatar
      savvyt
      Frequent Visitor

      hi nielsvdc , thanks for your reply. I checked and yes you could still see the activity progress table when you run the notebook manually, but you could no longer see it when you run the notebook from pipeline, so it's not DAG configuration error.

  • I have only seen it in interactive runs and it is never visible in run history snapshots.

    • savvyt's avatar
      savvyt
      Frequent Visitor

      g3kuser it was previously visible in history snapshots, it took like 2-3 seconds to load, but from 2-3 days ago it totally disappeared and only left an empty row. It was actually useful since it helped us to find root notebook that has failed. Now, to find the output message of the particular failed sub-notebook/table, you have to manually go through all of the sub-notebooks in the left bar until you find the one which has failed.

  • v-prasare's avatar
    v-prasare
    Community Support

    Hi savvyt , 

    As of now, there is no public-facing detailed documentation directly from Microsoft specific to runmultiple(). as you mentioned, It was actually useful since it helped users to find root notebook that has failed
    I’d encourage you to submit your detailed feedback and ideas via Microsoft's official feedback channels Microsoft Fabric Ideas and upvote. Feedback submitted here is often reviewed by the product teams and can lead to meaningful improvements 

     

     

     

     

    Thanks,

    Prashanth Are

    MS Fabric community support

  • v-prasare's avatar
    v-prasare
    Community Support

    We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

    If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

    Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

     

    Thank you for your understanding and participation.