Fix for init failure recovery (only applies when baking the failed in…#1929
Merged
Fix for init failure recovery (only applies when baking the failed in…#1929
Conversation
Tim-Linschoten
approved these changes
Nov 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes a very specific case where an instance is baked twice.
On second bake an actor is found and the Init event is applied again (in case it did not reach on the first bake) but this time with empty metadata which result in an Instance that is ready to receive commands but has no metadata.
Note: The second bake can not overwrite metadata from a successful first bake since once initialised the Instance will ignore further Init events.
So we now fix the case: Instance first bake -> Actor created -> Init Message lost -> baked again