We are having the same issue. Additionally, whenever we edit an existing flow with an automation object, for example create job, parameters are cleared and the work flow breaks.
I am experiencing the same issues. An already correctly running flow, stopped working and cannot be repaired, due to the error: "failed to fetch: getrunbook"
Hi @ Ivazquez,
I have made a test and the issue is confirmed on my side.
If I choose a Runbook in the “Runbook Name” field of action “Create job” , the action would pop up the error
“Failed to fetch: GetRunbook”
I would post this issue to my product team, if the issue is solved, I will reply here.
Could we please get an update on this issue? This is causing all sorts of processing issues within our tennant causing end-user complaints!
Verify the account register to perform the flow and the account that process the runbook, I granted permission and license the account that runs the flow and runbook and it started working again after replication.
@Alice Zhang is there any update on this. It is not like this is pre release functionality that was broken. This is general release and should be made a priority. Please update.
I am all licensed up, deleted and recreated the whole flow multiple times. All permissions are right. I get the same result: "Failed to fetch: GetRunbook"
@Anonymous I tested it on several devices with/without VPN but I had no luck..
This time I used a new user with a complete E3 License and Owner role on the subscription, in my Case it doesn't help.
This all of a sudden works now, but I am not allowed to set the parameters for the runbook anymore. When in the flow I was able to pass values to the runbook parameters but that option does no longer exist, any idea on another approach / alternative?
I still get the Failed to fetch: GetRunbook error message. I created a new runbook and copied the powershell code. There is no change.
This Flow ran fine 10 days ago but now it is broken and I also see the syntax of runbook with powershell has changed.
Does anyone here know what changed and why this is all of a sudden not working? I havent seen any response from Microsoft on this or is it not there responsibility to answer on this forum?
Many congratulations to the Season 1 2021 Flownaut Crew!
Check out our new profile badges recognizing authored solutions!
Check out the community blog page where you can find valuable learning material from community and product team members!