Forum Discussion
Workspace Identity not authenticating to Invoke Pipeline
Hi KimMW,
What you're doing should be working to the best of my knowledge.
I just tried this in my enviornment, and it works without issue.
My setup:
One pipeline that sends an email and triggers the second pipeline
the second pipeline just sends an emailThe connection in my invoke pipeline activity looks like this:
And this works without issue.
Note that if the workspace identity only has viewer, I do get the error you are describing.
But your workspace identity does have contributor, which works on my end.
Are you able to make a new pipeline and test it? I wonder if there is something weird with your existing pipeline.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Super UserHi KimMW,
First, are you using the new pipeline activity and not the legacy one? The legacy one won't work for this.
Can you send a screenshot of the workspace identity tab of the workspace settings for your workspace so we can confirm?
If the workspace identity has the contributor role, everything *should* be working.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Hi tayloramy
Yes, I can confirm that I am using the new invoke pipeline action rather than the legacy one.
Here is the screenshot of the workspace identity tab
- tayloramy
Hi KimMW,
What you're doing should be working to the best of my knowledge.
I just tried this in my enviornment, and it works without issue.
My setup:
One pipeline that sends an email and triggers the second pipeline
the second pipeline just sends an emailThe connection in my invoke pipeline activity looks like this:
And this works without issue.
Note that if the workspace identity only has viewer, I do get the error you are describing.
But your workspace identity does have contributor, which works on my end.
Are you able to make a new pipeline and test it? I wonder if there is something weird with your existing pipeline.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
