Coordinator metric "Highest proven consecutive aggregation block number" doesn't update correctly

[jonesho]

🔐 🔐 Should this be a security advisory instead? 🔐 🔐

We notice on mainnet, there was an occasional incident that coordinator metric "Highest proven consecutive aggregation block number" didn't update correctly, it should be 24826777 as "Highest proven aggregation block number" but still instead it stayed at 24822667 which was the last L1 finalized block number atm. At the time the screenshot was took, the aggregation for 24822668..24826777 had already been submitted but without "finalized" tag on L1 yet.

Impact

environment [Testnet/Mainnet]

an user is impacted [Y/N], if yes type of user: [External/Internal]

Describe the bug

Steps to Reproduce

Can't find a way to reproduce yet, will try to create a local test to reproduce

Steps to reproduce the bug:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Actual result

Evidence of the bug including log extracts, screen shot, wallet addresses, Tx hash, ...

Expected result

A clear and concise description of what you expected to happen.

Remember that an issue without proper labels and without assignee is unlikely to get prioritized -> contact the team or the product owner to get it included in the plan.