cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Exporting PowerApps packages error: The operation for object was not found

Hi everyone. We have a serious issue and would like some urgent help. Any comments will be highly appreciated.

 

The summury

Today it is no longer possible to export PowerApps in the Canadian envrionments.

The error is always the same, no matter wich Office 365 tenant we tested:

The packaging operation with ID 'a0ca10e6-fff6-414a-9c93-1b043d09c21f' was terminated after too many failures. The error message is: '{ "error": { "code": "AzureResourceManagerRequestFailed", "message": "The request failed with error: '{\"error\":{\"code\":\"OperationNotFound\",\"message\":\"The operation '4a265643-34fb-4c04-b390-a8df19302137' for object ID '2e5a0379-cbf3-415b-a465-2bf265a33d56' was not found.\"}}'. The tracking Id is 'bde3b78a-1ea6-43bc-a3e5-479f7dcce31c'." } }'

 

PowerAppsExportIssue_1.png 

 

PowerApps export error.png

 

More info

- US Environments allow us to export PowerApps

- It does not matter which PowerApps we export. Even if you try to create a blank PowerApp with no connectors - we cannot export it

- Instance version: 9.1.0.28 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
PowerApps Staff CWesener
PowerApps Staff

Re: Exporting PowerApps packages error: The operation for object was not found

Hi @DenisMolodtsov - can you please retest this? We've made some changes to hopefully mitigate this issue.

Thanks,
Clay.

View solution in original post

5 REPLIES 5
PowerApps Staff CWesener
PowerApps Staff

Re: Exporting PowerApps packages error: The operation for object was not found

Thanks Denis! We are looking into it now.

Thanks,
Clay.

Re: Exporting PowerApps packages error: The operation for object was not found

About 30-60 minutes ago we no longer experience the issue when exporting PowerApps packages. We have tested it in two different Office 365 envrionments where it was failing yesterday.

 

It was still failing aboit 2-3 hours ago, but now it's all good. 

 

In case someone is wondering - we didn't change anything to fix it. It appeared and went away without our involvement. We will still keep the MS ticket open for a day or so in case the issue comes back, but we are already glad to be able to export PowerApps. We needed it to promote our work to QA and Staging environments.

 

 

UPDATE: The issue is back now. We cannot export again.

UPDATE #2: The issue was solved at our envrionments. We can now export.

Highlighted
PowerApps Staff CWesener
PowerApps Staff

Re: Exporting PowerApps packages error: The operation for object was not found

Hi @DenisMolodtsov - can you please retest this? We've made some changes to hopefully mitigate this issue.

Thanks,
Clay.

View solution in original post

Re: Exporting PowerApps packages error: The operation for object was not found

@CWesener We have tried it a minute ago. It seems to be working fine. We were able to export with no issues

PowerApps Staff CWesener
PowerApps Staff

Re: Exporting PowerApps packages error: The operation for object was not found

Great to hear, @DenisMolodtsov - please reach out if you see any other problems.

Thanks,
Clay.

Helpful resources

Announcements
thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

Top Kudoed Authors (Last 30 Days)
Users online (5,011)