Forum Discussion
Resolver IIIFabric notebook when run via ADF pipeline trigger run issue
Thanks apturlov and BhaveshPatel for the inputs. The underlying issue was related to the DDL creation issue of one of the staging tables. However, as we used webactivity to invoke fabric notebooks, we could see some timeout issues, due to presence of parent and multiple child notebooks. We did increase the timeout in webactivity in ADF as well as in the child notebook call. This helped us to run the child notebooks completely and successfully. The ideal way will always be utilizing fabric pipelines and its notebooks so that the compute and connection strings remain in one environment to avoid the integreations issues. As webactivity coming out of ADF can have fabric notebook API call limitations which is be avoided in fabric.
Hope this helps other users who are working on the similar objectives.
Super UserHi ati_puri, in your scenario you invoke a Fabric Notebook using Fabric's REST API through external ADF pipeline using a Web activity. Key difference here is that the Notebook is invoked via Fabric's REST API compared to a manual Notebook run via Fabric's UI. I don't have hands-on experienc like that but from your description it looks like the Notebook does not have a Lakehouse destination set when invoked via API. I assume you know that a Notebook in Fabric must have a default Lakehouse to run successfully. Can you check what Lakehouse the Notebook is connected to when invoked via REST API? Also I would want to eliminate potential impact of the ADF's Web activity and try and trigger a Notebook using a REST API directly without ADF from a REST Client, for example.