Forum Discussion
Invoke Pipeline Returns "Could not found the requested item"
I'm having issues with the Invoke Pipeline(Preview) activity where I am getting the error {"requestId":"e9e54d07-8d30-4de4-b3f4-3be3ad15a476","errorCode":"ItemNotFound","message":"Could not found the requested item"}
To test this issue, I set up a:
- A pipeline with the only activity in it being Invoke Pipeline(Preview)
- No parameters - The original pipeline I set up had parameters and I was getting the same error code so I tried to remove it to see if it was a parameter issue
- A child pipeline with the only activity in it to Get Metadata for a table in a lakehouse
- No parameters
- This pipeline will successfully run on its own
When I run #1 I get the error message {"requestId":"e9e54d07-8d30-4de4-b3f4-3be3ad15a476","errorCode":"ItemNotFound","message":"Could not found the requested item"} however I'm not sure why the Item would not be found since I was able to specify it. I am attaching my configuration settings as screenshots to this post. Did I miss something in the Invoke Pipeline settings?
Parent Pipeline
Child Pipeline
I figured out the issue, it is due to a directory issue. I was working on a client's Fabric instant using a guest external account. Fabric kept thinking that I was in my own Fabric environment instead of the client's which and pipeline would have been missing from my own environment.
The solution I found was having my client set up a Fabric pipeline connection instead of using my own and selecting it as the first step in the invoke pipeline activity.
6 Replies
Hi Anonymous ,
Here are some of my personal thoughts on your question:
1. I noticed on your first screenshot that it says “Currently Pipeline return values is only supported with ADF & Synapse pipelines. To fetch pipeline return value for To fetch pipeline return value for fabric pipelines, please use invoke Pipeline(Legacy)”. This indicates that this feature is not supported in the current Fabric pipeline. So I think you can either use ADF or Synapse.
2. I also think you need to verify that the account running the pipeline has the necessary permissions to access the parent and child pipelines. Make sure that the resources (e.g. the table at the lake house) are available and accessible while the pipeline is running.
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I figured out the issue, it is due to a directory issue. I was working on a client's Fabric instant using a guest external account. Fabric kept thinking that I was in my own Fabric environment instead of the client's which and pipeline would have been missing from my own environment.
The solution I found was having my client set up a Fabric pipeline connection instead of using my own and selecting it as the first step in the invoke pipeline activity.
I ran into the same issue and found a more specific solution that worked for me.
The root cause is the same — working as a guest user in a client's Fabric tenant — but the fix goes one step further than just using a Fabric Data Pipeline connection.
When creating the Fabric Data Pipeline connection in the Invoke Pipeline activity, do NOT sign in directly with your guest account when the login popup appears. Instead:
1. Choose "Sign in with another account" (or "Use a different account")
2. Select the option to sign in to a specific domain
3. Enter the client's tenant domain explicitly
4. Then sign in with your guest user accountWithout this step, Fabric authenticates the connection against your home tenant even if you have already switched directories — which is why the pipeline cannot be found. By explicitly specifying the target domain during connection setup, the connection is correctly scoped to the client's tenant and the Invoke Pipeline activity resolves the child pipeline without issues.
Hope this helps anyone running into the same problem!
