Unanswered

AsyncOperation table file capacity growing in Sandbox environment

(0) Share

Report

Posted on by sb_teal

128

We have a Sandbox environment for which the AsyncOperation table file capacity is growing - this environment has very little traffic, and there are no classic workflows in the environment so I don't understand why the file capacity is growing. I have tried to delete completed system jobs following instructions here https://learn.microsoft.com/en-us/power-platform/admin/cleanup-asyncoperationbase-table but my jobs go straight to a Cancelled state and don't actually run. I have Power Platform administrator privileges and this environment was created by me, so I believe I have sufficient privileges.

The sandbox environment is only used to test new versions before migrating to production. I'm thinking that seeing as I can't delete the competed system jobs then perhaps I delete the environment. My question is - if I delete the environment will this definitely free up the file capacity?

Categories:

Governance & administering

I have the same question (0)

All responses (2)

Answers (1)

eleung83 232 on at

Like (0)

Report

You can delete the completed system jobs. You can just setup a recurring bulk delete job if you want to get rid of this records (Usually you'd setup a job to get rid of completed system jobs completed before a certain date, so you could keep some for any other miscellaneous purpose.

This table contains records for any asynchronous jobs that e.g. rollup fields calculations, asynchronous plugins, existing bulk delete jobs, essentially anything that runs asynchronously against that environment and is directly part of the environment e.g. workflows, fields, plugins etc

You can delete the environment as well if you wish and it should free up the capacity. I can't recall if there's a day delay for the space allocation to refresh in the admin portal

Was this reply helpful? Yes No
Verified answer

sb_teal 128 on at

Like (0)

Report

I tried to create a bulk delete job many times but the status of the job always went straight to cancelled. I manually deleted completed system jobs through the UI. I waited 36 hours (the Microsoft docs say it can take up to 24 hours for the capacity to refresh) but the capacity for AsyncOperation table file capacity was still there and growing. I ended up deleting the environment (as it is a Test environment) because it seemed the easiest fix, obviously that would not be an acceptable solution for a production environment. The same solution is in a dev and production environment and neither of them have capacity issues.

Was this reply helpful? Yes No