| Previous | Next |
| UI_E_TRANSITION_NOT_IN_STORYBOARD | UI_E_TIME_BEFORE_LAST_UPDATE |
UI_E_TRANSITION_ECLIPSED
Within Windows Animation Manager, UI_E_TRANSITION_ECLIPSED reports that one transition’s timing would hide the beginning of another transition. Diagnosis of this result should follow the original owner and generation rather than treating the visible symptom as the cause.
Facts that change the diagnosis
| Capture | Diagnostic value |
|---|---|
| Both transition identities for this HRESULT. | This separates caller input from environment and service state and helps test the Windows Animation Manager boundary. |
| Start and completion keyframes for this HRESULT. | This provides a stable comparison across retries or another machine and helps test the Windows Animation Manager boundary. |
| Durations and priority result for this HRESULT. | This identifies the exact object or resource generation involved and helps test the Windows Animation Manager boundary. |
| Resolved overlap interval for this HRESULT. | This places the failure on the lifecycle or transaction timeline and helps test the Windows Animation Manager boundary. |
Subsystem meaning
During a this result investigation, Windows Animation is a stateful COM subsystem. 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.
Transition ordering can be syntactically connected but temporally ineffective., an earlier transition or keyframe relation may consume the period in which a later transition is expected to start.
The first owner to inspect is the animation manager, storyboard, transition, timer, or callback that returned the HRESULT.
Isolation workflow
When it is returned, use a disposable control object, repository copy, file, or device association where the subsystem permits it.
- First: Plot the two intervals on one timeline.
- Next: Remove priority relationships as a control.
- Then: Shorten neither transition until the intended ordering is explicit.
- Finally: Validate the later transition receives a nonempty interval.
Avoid the tempting broad fix
During a this result investigation, UI_E_LOOPS_OVERLAP concerns repeat sections; TRANSITION_ECLIPSED concerns the start of a specific transition.
Do not treat the invisible transition as a renderer or opacity problem before checking its time interval.
Expected branches
| Control | Interpretation | Hold constant |
|---|---|---|
| Same input, fresh object or connection | If the result disappears, retained lifecycle or ownership state is implicated. | While diagnosing this result, keep the original data, account, device, or timeline parameters unchanged. |
| Same object, reduced operation | If the result follows one specific transition, statement, file, or ceremony step, the failure is localized. | While diagnosing it, remove only unrelated work and keep the first failing boundary visible. |
| Same operation, controlled environment | If the result follows one machine, account, volume, network, or device, environment matters. | While diagnosing it, keep versions and identity explicit rather than comparing only the final message. |
Regression proof
Verify it with the original scenario, one boundary case, and one deliberate failure; success means every intended transition has a positive scheduled interval and becomes observable in a deterministic timeline test.
Technical references
The references below define the API family or storage/protocol behavior used to interpret it.
- Microsoft: Windows Animation error codes
- Microsoft: IUIAnimationManager interface
- Microsoft: IUIAnimationStoryboard interface
- Microsoft: IUIAnimationTransition interface
Looking for a different code? Search another status or error code.