| Previous | Next |
| UI_E_STORYBOARD_ACTIVE | UI_E_START_KEYFRAME_AFTER_END |
UI_E_STORYBOARD_NOT_PLAYING
Within Windows Animation Manager, UI_E_STORYBOARD_NOT_PLAYING reports that a playback operation targeted a storyboard that is not currently playing. Diagnosis of this result should follow the original owner and generation rather than treating the visible symptom as the cause.
Mechanism behind the code
Pause, resume, finish, or status-dependent control requires a scheduled storyboard in the appropriate state. A storyboard definition can be valid and complete while not being in playback.
High-value telemetry
- Requested control operation.
- Storyboard status immediately before it.
- Schedule result and time.
- Prior cancel, abandon, or completion event.
Decision table
- 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 requested control operation and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: check Schedule and its HRESULT. Hold constant: keep the original failing sample available for the final regression test.
Safe reduction procedure
Use a disposable control object, repository copy, file, or device association where the subsystem permits that safely.
- First: Check Schedule and its HRESULT.
- Next: Gate playback controls on current status.
- Then: Record completion and cancellation transitions.
- Finally: Create a state-machine test for schedule-play-complete.
Do not erase the distinction
During an investigation, UI_E_STORYBOARD_ACTIVE rejects operations that require inactivity; NOT_PLAYING rejects operations that require playback.
Do not call Resume as a substitute for initial Schedule.
Successful outcome
Verify it with the original scenario, one boundary case, and one deliberate failure; success means the control is accepted only in its valid state and invalid transitions are handled without retry loops.
Technical references
Looking for a different code? Search another status or error code.