| Previous | Next |
| UI_E_END_KEYFRAME_NOT_DETERMINED | UI_E_TRANSITION_ALREADY_USED |
UI_E_LOOPS_OVERLAP
The scope of UI_E_LOOPS_OVERLAP is Windows Animation Manager: two repeated storyboard intervals overlap in an invalid way. Preserve 0x802A0105 beside the returning call before cleanup or retry creates a more generic secondary failure.
Read the boundary first
When it is returned, Windows Animation is a stateful COM subsystem. During a this result investigation, animation variables, transitions and storyboards are created under a manager, scheduled against a monotonic animation time, updated before drawing, and eventually sealed or released. A visible glitch can therefore be downstream of a lifecycle, ownership, timeline, callback, or numeric contract failure.
During a this result investigation, loop definitions introduce repeated time ranges. Nested or adjacent repeats must form a valid temporal structure; two loops that partially intersect create ambiguous ownership of the overlapping interval.
The first owner to inspect is the animation manager, storyboard, transition, timer, or callback that returned the HRESULT.
Keep neighboring conditions separate
When it is returned, UI_E_TRANSITION_ECLIPSED concerns one transition hiding another start; LOOPS_OVERLAP concerns repeated intervals.
Do not reduce repeat counts until the interval topology is corrected.
Incident record for this HRESULT
| Capture | Diagnostic value |
|---|---|
| Loop start and end keyframes for this HRESULT. | This provides a stable comparison across retries or another machine and helps test the Windows Animation Manager boundary. |
| Repeat counts for this HRESULT. | This identifies the exact object or resource generation involved and helps test the Windows Animation Manager boundary. |
| Resolved interval ranges for this HRESULT. | This places the failure on the lifecycle or transaction timeline and helps test the Windows Animation Manager boundary. |
| Transition membership inside each loop for this HRESULT. | This separates caller input from environment and service state and helps test the Windows Animation Manager boundary. |
Reproduce without destroying evidence
The investigation should change one variable at a time and keep the original failing sample.
- First: List every repeated interval numerically.
- Next: Remove one loop and validate the other.
- Then: Prefer proper nesting or disjoint ranges.
- Finally: Test one iteration before restoring repeat counts.
Three useful controls
- Fresh storyboard or animation object: for this HRESULT, a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: for this HRESULT, keep the timeline, transitions, and manager version fixed.
- Reduced failing operation: If this result follows the reduced step, the rejecting transition is localized. Hold constant: for this HRESULT, retain loop start and end keyframes and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: list every repeated interval numerically. Hold constant: for this HRESULT, keep the original failing sample available for the final regression test.
Definition of done
Closure for this HRESULT requires repeated sections are disjoint or properly nested and remain valid across all configured iteration counts; then repeat the next lifecycle operation to detect stale state.
Technical references
The references below define the API family or storage/protocol behavior used to interpret this result.
- Microsoft: Windows Animation error codes
- Microsoft: IUIAnimationStoryboard interface
- Microsoft: Windows Animation overview
- Microsoft: Schedule a storyboard
Looking for a different code? Search another status or error code.