# Restore state not working for DLNA extension

**URL:** <https://discourse.mopidy.com/t/restore-state-not-working-for-dlna-extension/4358>\
**Category:** Misc\
**Created:** [October 9, 2020, 11:01am UTC](https://discourse.mopidy.com/t/restore-state-not-working-for-dlna-extension/4358 "2020-10-09T11:01:29Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [October 9, 2020, 5:27pm UTC](https://discourse.mopidy.com/t/restore-state-not-working-for-dlna-extension/4358/4 "2020-10-09T17:27:42Z")

</div>

I think we already do restore the tracks regardless of the track availability and it’s the restoration of the playback state that causes the issue. i.e. If Mopidy was playing/paused when it was shutdown then it restarts playback from wherever it got to as part of the startup state restoration. You’d get the same thing if you removed/disabled a backend that had tracks in the saved state. But if you stop (not pause) before shutting down then I don’t think this issue occurs - is that right? (note that some clients/frontends will clear the queue as part of the stop request.) Do the tracks actually get removed from the tracklist or is it just the errors and if you wait for the DLNA server to turn up can you then play the tracklist?

---

_[View the full topic](https://discourse.mopidy.com/t/restore-state-not-working-for-dlna-extension/4358)._