Troubleshooting · How we test and maintain this guide
A refusal is different from a slow transfer
The source can refuse a request before usable audio arrives. The current upstream adapter distinguishes a sign-in requirement, a refusal or verification requirement, and a rate-limit response. Those cases are not repaired by changing a filename or selecting a different output format. The visible message should guide the next step.
| Response class in controlled handler checks | Workspace meaning |
|---|---|
| 401 from the source | The song needs source-service sign-in |
| 403 from the source | Access was refused or verification is required |
| 429 from the source | Requests are being rate limited |
| Reviewed TuneBundle song restriction | This identified song is unavailable through this tool |
| Ordinary missing song | The source is not found or is not publicly available |
This table describes how the tool handles those conditions. It is not a report that the platform currently returns them for your account or a claim that every 403 has the same cause. The source's own page and the exact error provide the relevant context. A successful visit while signed in can differ from public access available to an independent tool.
Stop repeated requests and preserve what is ready
For an upstream access or rate-limit response marked as blocking, the batch pauses remaining requests. It keeps already prepared results instead of discarding them. Save those useful files individually or as a selected ZIP, and export the CSV if you need a record of the unfinished rows. A paused batch is not an instruction to restart every successful song.
- Read the message and distinguish a source access problem from an ordinary transient error.
- Check the intended song in the official service. Confirm that it is complete and publicly accessible where expected.
- If sign-in is required, use the official options available to you. Do not paste cookies, passwords or private session credentials into TuneBundle.
- If the message is a rate limit, wait before manually trying again. The tool does not promise a universal reset interval.
- Retry the affected subset only when there is a reason to expect a different result.
Changing networks, share-link spellings or accounts to evade a restriction is not a troubleshooting step this guide recommends. A smaller batch can reduce local work, but it does not grant access to a song that the source is refusing. Save the evidence you need and avoid turning a single refused request into a repeated loop.
A reviewed rights restriction has its own process
TuneBundle can restrict an identified song after a rights report has been reviewed. A submitted email does not automatically create a restriction. The maintainer records a decision for the relevant identifier and deploys that decision. The checks cover canonical links, resolved share links and new uses of previously signed service tickets. Restricted playlist entries are marked unavailable.
A per-song reviewed restriction does not require unrelated songs in the batch to be refused. The controlled tests verify that distinction. If the identification is mistaken, use the review and dispute process with the affected URL, case reference where available and relevant supporting information. Do not try alternate share addresses as a way around the same decision.
Restrictions apply to the service requests and site material under TuneBundle's control. They cannot erase a file already saved to a computer or revoke a public source address already disclosed elsewhere. The reporting page explains those practical limits and does not claim that the maintainer can remove a song from Suno itself.
Make a useful support report
State the exact message, whether it appeared while importing a playlist or preparing audio, the approximate time and your browser version. Say whether one song is affected or several, and whether already ready files remain usable. If comfortable, include the public URL; do not include private media, account credentials or temporary playback tokens.
For a rights concern, use the reporting process rather than an ordinary performance complaint. For a technical refusal, describe the observed behaviour without assuming its legal cause. Keeping those reports separate lets the maintainer investigate the right question and avoids treating a transient network failure as a copyright decision.