James Simone

@JakMGitHub I'm wondering if this is a similar issue to the one we are talking about in #523 - essentially, in the first log file (the `SerialBatchApexRangeChunkHandler` one), I can...

@JakMGitHub for your use case, I would _highly_ advise using the default value functionality for new records without children. Apex Rollup won't "know" about parent-level records until it's in a...

It seems to me that the default value in conjunction with your scheduled run of the full recalc would suffice; only records with children would have their values updated to...

@JakMGitHub are you still experiencing this issue?

@louisskelton that's not that much data volume at all, but in 1.7 the full recalculations moved over to always using Queueables to get around some limitations with Batch Apex. Do...

@louisskelton based on my initial experiments, this is probably due to large swathes of the "batch" not requiring state records. It's hard to track the ongoing status of the job...

@louisskelton something that might help is enabling the `Should Skip Resetting Parent Fields` flag on the org default rollup control - you can also try lowering the `Batch Chunk Size`...

Additional info - I added some logging into my own `RollupFullBatchRecalculator` instance just to see what was going on with both of the concurrent calculations I have running - one...

@louisskelton are there ever instances where the lookup field on that child item is null? Line items without opportunities? Just thinking out loud here about possible where clauses that might...

Hey, I will take a look at this, I saw this happening in one of my orgs the other day as well and was quite surprised to find it still...