Troubleshooting · How we test and maintain this guide
Restored input is not restored audio
The workspace can remember input text, mode, format and naming choice within the browser session. It does not put prepared audio files or built ZIPs into that session-storage record. Those larger objects live temporarily in the open page. Reloading the page creates a new workspace, even when familiar source links reappear in the text area.
| Item | After a refresh |
|---|---|
| Input links and choices | May be restored from session storage |
| Prepared audio and previews | Must be prepared again |
| Built ZIP object | Must be built again from newly prepared results |
| Files already saved to disk | Remain in the destination you chose |
| CSV saved to disk | Remains a record, not a copy of the audio |
Our recorded browser check refreshed a workspace and verified that its input links returned without automatically fetching audio. This protects against an unexpected new download run on page load. It also explains why seeing the old text is not evidence that the old results are still available. The tool waits for another explicit preparation action.
Recover from saved evidence first
- Check the browser's download history for files that completed before the refresh. Open their actual destination.
- If you saved a ZIP, inspect that archive and the CSV inside it. Do not start another run simply because the page looks empty.
- If only a CSV remains, use its source URLs and statuses to identify what still needs to be prepared.
- Recheck the current availability and permission for those songs. An old successful row is not a permanent access guarantee.
- Prepare a small missing subset, save it, and keep the new export separate until it has been compared with the older files.
Selection checkboxes belong to the prepared results. Do not assume your earlier chosen subset will be reconstructed from restored input text. Reapply the intended selection and naming choice before building the new ZIP. The earlier CSV can help explain the selection, particularly when several takes share a title.
If no links or files remain, recovery depends on your own source records or the original service. TuneBundle does not offer a server-side download-history account or a private-library backup. A temporary preview URL from a closed page cannot stand in for the source song URL. Save stable source references in a record you control.
Different kinds of storage fail differently
Session storage, browser memory and free disk space are separate resources. A browser policy that prevents saving small session settings can stop input restoration; it does not mean the server lost a permanent music library. A memory shortage can interrupt conversion or ZIP assembly. A disk-space problem can prevent the final browser save even though preparation succeeded.
The current code handles a failure to read or write the settings record without deliberately blocking the core workspace. That is an implementation boundary, not a claim that every private-browsing mode has been tested. If links do not return, keep a separate source list and save results before leaving. There is no need to weaken privacy settings merely to preserve a few input choices.
Clearing site data is a poor first troubleshooting step when your only source list is still in the tab. Save the useful files and export the CSV first. If support later asks for a clean session, use a separate test window and a small reproducible example, leaving your working collection intact until its files are safe.
Finish a session deliberately
Before closing the page, check that the intended tracks are selected, that a revised ZIP was rebuilt after any change, and that the actual browser save completed. Open the destination folder and verify at least the files you will immediately use. Keep tracks.csv and manifest.json alongside the collection rather than treating their small size as a reason to discard them.
For longer projects, maintain an independent source list and a clear export date in your folder naming. A local archive is recoverable only if you can find and read it. Once the saved files and records have been checked, closing the temporary workspace is an ordinary finishing step instead of a risk to the only copy of your work.