The CCM Cumulus job is failing or producing stale/missing cost data.<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The Cumulus job is responsible for aggregating billing data processed by the CCM Infra Stack (Fenix). Each successful deployment of the Fenix layer writes a deployment hash to the fenix_manifest record. If this hash is missing, outdated, or mismatched, the Cumulus job may fail silently or error out during execution. Steps to Verify Navigate to the fenix_manifest table on your instance: <your_instance_url>/fenix_manifest_list.doConfirm a record exists and check the deployment hash field. It should reflect a recent timestamp consistent with your last CCM Infra Stack update or deployment.If the hash is missing or stale: Verify the CCM Infra Stack plugin is active and up to date under System Applications > All Available ApplicationsCheck for any failed upgrade or mid-deployment rollback in System Diagnostics > Upgrade HistoryIf the Infra Stack was recently updated, allow up to 15–30 minutes for the manifest to repopulate, then re-check Once a valid hash is confirmed, navigate to Cloud Cost Management Workspace and manually trigger the Cumulus job execution.Monitor the job status. If it transitions to Failed again despite a valid hash, pull the execution log and note the first ERROR-level entry for attention and note when it was last updated.