Error validating Execution Restrictions - Bad Execution Restrictions

[Jose_Malan]

AzureBlobStorage.CreateFile failed: { "error": { "code": 400, "message": "Error validating Execution Restrictions - Bad Execution Restrictions", "source": "europe-002.azure-apim.net", "path": "choose[3]\\when[1]\\choose\\when[1]", "policyId": "", "clientRequestId": "9227fcd6-8b6b-4117-9957-3e69cdb6c50b" } }

I deleted the data source and reconnected, but it's not working.

Until April 2nd it was running on version 3.24032.26. From version 3.24034.17 the problem started.

[MikeyMole]

Hi All,

I am also seeing this exact problem with Blob Storage connection when using later authoring version. @microsoft this is a serious problem because it will eventually prevent me from deploying production apps until this is fixed.

Please resolve!

Thanks

[LanceDelano]

Also, as I noted, the problem is with dangling connector references. We are working on a fix to clean this up automatically on save.  I don't have an ETA for this yet though. 

[wyotim]

Hi @LanceDelano, thanks for the replies and engagement in this thread. Would you mind explaining what "dangling connector references" means? I guess I'd like to know if there is something that can be done to avoid this situation in the future on our end or not. No worries either way, I'm just curious to know more.

Again, thanks for the replies! It is appreciated!

[kabhinav150]

A possible workaround for this is to enable the retired setting. please check the media. but before trying this try to work by downgrading the app or re-connecting the connector. as this is a retired setting, but this is the workaround given by Microsoft.

1)

[Rana]

@kabhinav150 ,

Thanks for the workaround. The emails are working. Do we have any update from Microsoft when this will be fixed? 

Regards,

Rana

[kabhinav150]

No.

[MikeyMole]

Just spoke with MS Support, no ETA currently on fix but they're working on it. When/if they tell me of authoring version with fix, I will post here unless someone gets there sooner 🙂

[Marco796]

I have the same issue. Setting back the Version and re-adding the connector didn't do the trick for me here.

Let's hope that MS will fix it soon.

Thanks in advance!

[mrscherry2000]

I have had the issue reappear and am now unable to revert and get it functioning again.  This application and connector is a core piece of our Daily Business Operations and is putting things at a standstill for us.  Need a fix ASAP.

[MikeyMole]

@Marco796 it should work.

I would try the following (I found this helped when I did it):

1. Open editor, change the authoring version back to 3.24032.26. The editor will close and re-open.

2. Confirm that the editor has successfully changed to version 3.24032.26.

3. Make a small non-material change to the app (add a label) and save the app.

4. Delete the Azure Blob Connector, and then re-add

5. Make a small non-material change to the app (add a label) and save the app.

6. Delete your small changes, and re-publish the app.