Forum Discussion
New “Invoke Pipeline (Fabric)” activity not executing, while Legacy version works
Hello Mauro89,
In the legacy setup, invoking the pipeline did not require a connection, which is why it was working there. In the new setup, invoking the pipeline activity requires a connection, and this appears to have been the cause of the issue.
After switching to a Service Principal connection, the new pipeline activity is now working as expected.
Thank you for your time and support—it was very helpful.🙂
Hello Mauro89 ,
I have created two pipelines in Microsoft Fabric:
A main pipeline, which invokes a child pipeline using the InvokeFabricPipeline operation
A child pipeline, which is a simple pipeline with no parameters or activities (for testing purposes)
However, when executing the main pipeline, I consistently receive the following error:
Error message
{"requestId":"3bd6a7a5-3fd3-420c-807a-f25ac091243e","errorCode":"ItemNotFound","message":"Could not found the requested item"}
Input
{
"waitOnCompletion": true,
"operationType": "InvokeFabricPipeline",
"pipelineId": "1b82c51a-66ca-49ce-b249-c8757c986af1",
"workspaceId": "31dae79c-d0be-478d-a752-22849953c41f",
"parameters": {}
}
Output
response header
{"Pragma":"no-cache","Transfer-Encoding":"chunked","x-ms-public-api-error-code":"ItemNotFound","Strict-Transport-Security":"max-age=31536000; includeSubDomains","X-Frame-Options":"deny","X-Content-Type-Options":"nosniff","RequestId":"3bd6a7a5-3fd3-420c-807a-f25ac091243e","Access-Control-Expose-Headers":"RequestId","request-redirected":"true","home-cluster-uri":"https://wabi-india-central-a-primary-redirect.analysis.windows.net/","Cache-Control":"no-store, must-revalidate, no-cache","Date":"Fri, 20 Mar 2026 11:11:36 GMT","Content-Type":"application/json; charset=utf-8"}
Manage Connections
Clarifications:
Both pipelines are in the same workspace
I have Admin access to the workspace
The pipelineId and workspaceId were copied directly from the Fabric UI
The child pipeline is saved and visible
A valid connection is configured via Manage Connections (screenshot attached)
Request:
Could you please help clarify:
If there are any additional backend requirements (e.g., publishing state, hidden dependencies, or API limitations) for invoking a Fabric pipeline
Whether InvokeFabricPipeline has any known constraints related to workspace scoping or connection binding
If this error could indicate an issue with ID resolution on the service side, despite the item being present and accessible
Hi aayushiharalal,
the invoke pipeline acitivty is basically very simple. There are not specific limitations like you mentioned.
What else you can try.
- Take you the legacy invoke (not sure if you call in both acitivities the same pipelines to invoke).
- OR create two complete new pipelines and invoke the one from the other just to check if there is any general issue in your environment
Best regards!
Hello Mauro89 ,
I’ve already tried creating a completely new pipeline for testing (as shown in the screenshot in above reply), but the issue persists.
Both Invoke Pipeline activities are calling the same pipeline. I also created a new connection to rule out any connection-related issues, but that didn’t resolve the problem.
Because of this, I’m currently unable to work across workspaces.
At this point, I’m wondering:
- Could this be related to tenant-level settings?
- Are there any capacity limitations or configurations that might cause this behavior?
I’m running out of possible causes to investigate, so any guidance on what to check next would be really helpful.
Thank you.
Hi aayushiharalal,
there is no tenant-level setting or capacity config which relates to the difference between the two activities.
Last thing what I can think of is that you check and compare both source codes of the pipelines. If there is nothing significant different, I recommend opening a support ticket at Microsoft.
Best regards!
Hello Mauro89,
In the legacy setup, invoking the pipeline did not require a connection, which is why it was working there. In the new setup, invoking the pipeline activity requires a connection, and this appears to have been the cause of the issue.
After switching to a Service Principal connection, the new pipeline activity is now working as expected.
Thank you for your time and support—it was very helpful.🙂