Rudder

In Rudder 8.2, when a node a deleted, there are errors in the logs

2025-03-03 09:50:38+0000 INFO  application.authentication - Rudder authentication attempt for principal 'admin' with backend 'file': success
2025-03-03 09:50:38+0000 INFO  compliance - [metrics] global compliance (number of components): 812 [p:0 s:160 r:0 e:1 u:0 m:0 nr:41 na:234 rd:0 c:93 ana:234 nc:49 ae:0 bpm:0]
2025-03-03 09:50:46+0000 INFO  policy.generation - Node 'windows-2019.priv.normation.com' (030cff71-1c1e-4aea-beaf-e14f209396aa) is a Windows node and a we do not know how to generate a hash yet
2025-03-03 09:50:50+0000 INFO  nodes - Node 'windows-2019.priv.normation.com' [030cff71-1c1e-4aea-beaf-e14f209396aa]' was deleted
2025-03-03 09:50:51+0000 INFO  nodes - Update in node '030cff71-1c1e-4aea-beaf-e14f209396aa' inventories main information detected: triggering dynamic group update and a policy generation
2025-03-03 09:50:51+0000 DEBUG dynamic-group.timing - Check if dynamic groups may need update (false): 2ms
2025-03-03 09:50:51+0000 ERROR nodes - Error when executing callback 'trigger-score-update' on node change event [deleted] node 'windows-2019.priv.normation.com' (030cff71-1c1e-4aea-beaf-e14f209396aa
)': Inconsistency: Cannot update node '030cff71-1c1e-4aea-beaf-e14f209396aa' score
2025-03-03 09:50:51+0000 INFO  policy.generation - Start policy generation, checking updated rules

Plus, it seems the policy generation is triggered before the node is deleted, but it should be the other way around