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’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.🙂
Thank you for sharing the update and resolution. Glad to hear that switching to a Service Principal connection resolved the issue.
If any of the responses helped, please consider acknowledging or marking it as the solution so it can help others facing a similar issue in the future.
