| 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 condition first
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.
Keep neighboring conditions separate
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
- Loop start and end keyframes.
- Repeat counts.
- Resolved interval ranges.
- Transition membership inside each loop.
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: a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: 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: 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: keep the original failing sample available for the final regression test.
Definition of done
Closure 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.
Looking for a different code? Search another status or error code.