Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added administration mode note #2375

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions power-platform/admin/cleanup-asyncoperationbase-table.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,9 @@ For synchronous workflows, we recommend enabling **Keep logs for workflow jobs t

:::image type="content" source="media/bulk-deletion-keep-logs.png" alt-text="Set Workflow Log Retention to keep logs for workflow jobs that encountered errors.":::

> [!NOTE]
> The bulk deletion job may be automatically canceled if the environment is in [Administration mode](/power-platform/admin/admin-mode#set-administration-mode).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would the right fix be to allow bulk delete jobs to execute in admin only mode? Is there a specific reason why we want to cancel bulk delete jobs when an org is in admin-only mode?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delayed response. I encountered this when troubleshooting an environment that was in administration mode and didn't realize it was causing the issue. I added the note in case anyone runs into the same issue in the future. Allowing bulk delete jobs in admin only mode might be a better option.


## AsyncOperation file capacity usage

Historically, the entire async operation context used to be serialized directly in the AsyncOperation table [Data property](/power-apps/developer/data-platform/reference/entities/asyncoperation#BKMK_Data), leading to quick growth in size if there are asynchronous plug-in registrations on large records (such as attachment). Since early 2021, the data portion of async operations is moved to file store. As a result, async operation data size is partially counted in database capacity and partially in file capacity. This helps reduce the cost (since file capacity is charged at a lower rate than database capacity) and improves overall performance (since queries against the AsyncOperation table are more performant).
Expand Down