Pipeline Notebook Activities Failing

[WilliamParker]

Starting mid last week we began having issues with Notebook activities failing in fabric our pipelines. The notebook activity fails after 3s - 6s. None of the attempts to execute a notebook from a pipeline are working, even when trying a new pipeline with a new notebook with minimal code. A session is not started so I am not able to see any of logs. No configuations were changed, we are able to run notebooks manually but not from our pipelines. I have seen others posting about a similiar issues and have not seen any clear resolutions as of yet. Please help, the limited error details we are receiving are showing below:

[12angrymentiger]

@Priyadarshi  Hi, I"m having the exact same issue today in the North Central US Region.

Can you help me resolve this?

[Priyadarshi]

Hi, Can you please help me with the activity run id of your notebook execution from Pipeline? you can retrieve it by selecting the same from the dropdown on the right side. Also, please confirm if your region is central US. 

[WilliamParker]

@Priyadarshi 

We are in the central us region. The activity run id from our notebook execution:

8c64e718-4e1b-403a-be93-3035dee2b57a

[Priyadarshi]

Hi, can you please check if you are still seeing the error?

[WilliamParker]

@Priyadarshi - Notebook activies are running from pipelines again. What was the root cause?

[v-cboorla-msft]

Hi @WilliamParker 

Following up to see if you are still facing the issue? And was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help .

Thanks

[WilliamParker · Accepted solution]

Notebook activies are working. However, I have no clue as to the actual resolution.

[v-cboorla-msft]

Hi @WilliamParker 

Glad that your query got resolved. Please continue using Fabric Community for any help regarding your queries.

[MartinMason]

This be very broke. Tried changing back to the older runtime and same error generated. Tried running the notebook with a parameter and different error encountered. Fabric may be GA now but in the US Central region, much problems still encountered...daily.