Troubleshoot missing audio lyrics

Troubleshoot missing audio lyrics is easier to verify when you use one controlled item and check the account, workspace, and destination at every step. This guide follows the current Dosya workflow and calls out the result you should see.

Before you start

• Open an audio file in the Dosya player in the current released client.
• Confirm the active account and workspace, then identify Lyrics panel for a track expected to contain lyrics.
• Use a small non-confidential test item and record its current state before changing it.
• Keep passwords, API keys, recovery keys, private links, and personal client data out of screenshots and support messages.

Steps: troubleshoot missing audio lyrics

1. Open an audio file in the Dosya player and confirm the active account and workspace.
2. Locate Lyrics panel for a track expected to contain lyrics and verify its name or identifying details.
3. Check embedded or synchronized lyric metadata and reload the track.
4. Read the displayed warning, permission, progress, or confirmation state before leaving the screen.
5. Confirm that lyrics display when supported metadata exists or the missing source data is confirmed.
6. Refresh or reopen the relevant view once to verify the result persisted.

Expected result

The controlled workflow completes and lyrics display when supported metadata exists or the missing source data is confirmed. The result remains visible after a refresh, reconnect, or return to the relevant screen.

Limits and important details

• Available controls depend on the current client version, account plan, workspace role, and policy.
• Processing, indexing, background transfer, or third-party authorization can delay a visible result.
• For destructive, access-changing, or automation actions, validate with disposable data before applying the workflow to important files.

Troubleshooting

The expected control is missing. Return to an audio file in the Dosya player, confirm the active workspace, and check that your role and client version support the action.

The operation is rejected or stalls. Read the exact message and check permissions, locks, storage, network state, source availability, and any third-party authorization before retrying.

The result is still unclear. Repeat with one small test item, then contact support with the time, client version, workspace, and a nonsecret error or request identifier.

Related guides

• Use media preview controls
• Manage the audio queue