Dry Runs are failing after account assignment changes

Products

• CloudHealth

Issue/Introduction

Sometimes, when you update account assignments, dry runs fail. This happens because of a temporary setting in the system related to account types.

Specifically, when account assignments are updated, the system temporarily removes the account type information. For dry runs to work, the account type needs to be set as either consolidated or standalone.

Cause

There is a routine process called the account scanner that runs regularly and fixes the account type information.

• If the account scanner runs after you update account assignments, dry runs will work fine.
• But if you try a dry run before the account scanner has run, it will fail because the account type is missing.

Since the scanner runs periodically, there can be a delay between when you change account assignments and when dry runs will work again.

Resolution

It’s recommended to wait up to 24 hours after making account assignment changes before running a dry run. This allows time for the scanner to update the account type properly.

Additional Information

Summary

• Account type is temporarily removed when you update account assignments.
• The system fixes this automatically with a scheduled scan.
• Dry runs fail if tried before this scan completes.
• Waiting 24 hours after changes helps avoid failures.