Flow failed to fetch: getrunbook

[Ivazquez]

Created a flow to trigger a runbook but everytime i add a runbook to the azure automation create job task an error pops up saying it failed to fetch:getrunbook! Is was working a few days ago but now all my automation flows are not working as configured.

[Ruebyn]

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.

[Anonymous]

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"

[azimmanjee]

Also having this issue.

[v-yuazh-msft]

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.

Regards,
Alice Zhang

[WillShea]

Any news on when this will be fixed.  It is affecting a production process.   Thanks,

[WillShea]

Is there somewhere that this can be escalated too?   This is causing me issues in production?  Please respond.

[Ruebyn]

Could we please get an update on this issue? This is causing all sorts of processing issues within our tennant causing end-user complaints!

[Ivazquez]

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.

[DiNO]

I've created a new flow with a new account (full permissions to runbook / Azure Automation) and the issue still exist 😞

[WillShea]

@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.

[Ivazquez]

Make sure the new account have flow license and that same account has automation rights within your subscription account.

[azimmanjee]

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 have the same issue, but it only happens when I am not connected to my company's VPN, or on my personal device.  Very strange.

[DiNO]

@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.

[shakonarson]

Has anyone gotten a solution on this, I am having the same issue and this is affecting production environment.

[shakonarson]

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?

[Ivazquez]

Once the runbook ia created the first time and the parameters are set and saved, the parameters are not listed anymore, you have to recreatw the flow again to be able to set the parameters again.

[shakonarson]

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?

[Ivazquez]

My mistake, what i meant was to recreate the flow task again not the actual runbook.