fix(history): skip update entity restoration#4302
Open
mgazza wants to merge 1 commit into
Open
Conversation
mgazza
force-pushed
the
fix/update-version-history-timeouts
branch
from
July 24, 2026 22:46
342448a to
790c8c9
Compare
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
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.
Summary
Problem
Update entities are generated at runtime and explicitly non-restorable. When an update entity has no current state during startup, attempting to restore it from entity history adds an empty lookup to HAHistory tracking. The tracker then retries that unnecessary lookup, producing avoidable backend load and timeout noise.
Tests
config_item_range_clampplugin_startuphahistoryRisk
load_user_configis a central startup path, but the behaviour change is restricted totype == "update". Regression coverage verifies normal history fallback remains active.