| Previous | Next |
| UI_E_WRONG_THREAD | UI_E_STORYBOARD_NOT_PLAYING |
UI_E_STORYBOARD_ACTIVE
UI_E_STORYBOARD_ACTIVE belongs to Windows Animation Manager. It marks the requested operation conflicts with a storyboard that is still scheduled. The useful starting point is the exact API, object and state transition that returned 0x802A0101, because a shell or application message can hide that boundary.
Where this result is raised
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. During a this result investigation, a visible glitch can therefore be downstream of a lifecycle, ownership, timeline, callback, or numeric contract failure.
When it is returned, an active storyboard remains part of the manager schedule even if a visual transition appears complete. During a this result investigation, structural reuse or release-sensitive operations must respect its reported status and completion lifecycle.
The first owner to inspect is the animation manager, storyboard, transition, timer, or callback that returned the HRESULT.
Evidence worth collecting
- Storyboard status and schedule time. for this HRESULT, this pins the event to an object or resource generation within the Windows Animation Manager boundary.
- Completion callback or abandonment result. for this HRESULT, this places the event on the lifecycle or transaction timeline within the Windows Animation Manager boundary.
- Attempted operation. for this HRESULT, this separates caller input from environment and service state within the Windows Animation Manager boundary.
- Manager update time. for this HRESULT, this creates a stable comparison across retries or another machine within the Windows Animation Manager boundary.
A controlled diagnostic sequence
During a this result investigation, reduce the case while preserving the condition described by the HRESULT.
- First: Query status before mutation or reuse.
- Next: Wait for completion or abandon through the supported API.
- Then: Use a new storyboard for overlapping work.
- Finally: Log the update that removes it from the schedule.
How to interpret comparison tests
| 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. |
What this code does not justify
UI_E_STORYBOARD_NOT_PLAYING is the opposite lifecycle mismatch for playback-only operations.
Do not infer inactivity solely from the current visual value.
Verification after correction
Treat it as corrected only when the operation is issued only after the storyboard leaves the active schedule, or uses a distinct storyboard; retain the original negative case so fallback cannot be mistaken for repair.
Technical references
The references below define the API family or storage/protocol behavior used to interpret it.
- Microsoft: Windows Animation error codes
- Microsoft: Windows Animation overview
- Microsoft: Schedule a storyboard
- Microsoft: IUIAnimationManager interface
Looking for a different code? Search another status or error code.