Deployment Pipeline Error Import failure: PyToIPynbFailure

[ShikeMarples]

Hello,

We've been using deployment pipelines for a couple months now with a few issues we've been able to figure out or workaround. Today, however, we are encountering a new error:

Import failure: PyToIPynbFailure. "Convert data from py to ipynb failed. Detail: PyToIPynb: the py format is not correct - The py content is not supported - prologue is invalid. Expected prologue: -- Fabric notebook source

Anyone seen this before and know of a cause/solution? This is a T-SQL notebook connected to a Warehouse.

Thanks in advance.

[ShikeMarples · Accepted solution]

I think there was something up with the service. Am able to deploy our notebooks again. We made no changes to the notebooks or our environment.

[v-aatheeque]

Hi @ShikeMarples 

Thanks for the update. We're glad to hear the issue has been resolved now.

If any of the responses shared in this thread helped you reach the solution, please consider marking it as the accepted answer. This will help other community members who may encounter a similar issue in the future.

[tayloramy]

Hi @ShikeMarples, 

I recommend submitting a ticket to Microsoft about this. I think T-SQL notebooks are not fully supported by deployment pipelines, but that is not documented anywhere. 

[GilbertQ]

Hi @ShikeMarples 

That is not something that I have seen before. What I would recommend doing is what happens if you create a new notebook and try send it through. What then happens?

[ShikeMarples]

Created a new workbook. Same error:

[DevLohp]

We experience the same issue while deploying to prod. But with normal basic notebooks. So is there an issue at MS side?

[GilbertQ]

I have not seen this before and would recommend you contact support.

Or you could try a basic notebook and see if that works?