Two Records in resource_aggregate_monthly Table for Same User, Plan, task and Month— OOTB Behavior?

[Captain Gaming]

Description:

Hi Community,

I'm observing something unusual in our PPM (Project Portfolio Management) setup and would like to confirm if this is expected Out-of-the-Box (OOTB) behavior or possibly a result of custom logic or a data issue.

🧩 Scenario:
In the resource_aggregate_monthly table, I noticed two records for the same:

user
Task
month_start
category = Project Actual
parent_category = Actual

One record shows 14 hours, and another shows 64 hours.
However, in Allocation Workbench, only 14 hours appear as Actuals, and when I drill down (click on the 14), it navigates to the correct detailed breakdown showing 64 total hours.

For January, only one monthly record exists (as expected), and the behavior is correct.

The issue is only happening for February.

🔍Investigative Steps Taken:

1. Checked resource_aggregate_weekly: All 64 hours for February are submitted and processed correctly.
2. Confirmed both monthly records were created at the same time & date.

❓Questions:

1. ✅ Is it expected OOTB behavior to have two monthly records with parent_category = Actual for the same user, resource plan, Task, and month?

2. 🔄 Could this happen due to the timing of weekly data submission vs. the monthly job?

3. 🧪 Has anyone else seen this behavior, and if so, how was it resolved?

4.📈 Why does Allocation Workbench display only the 14-hour record in the Actuals column and not the total 64?

Any insights, experience, or official guidance would be highly appreciated!

[jamesspradl]

I am having the same issue. Any fix for this?