Uploads and jobs
An upload is refused


A job failed
A failed job costs nothing. How to run it again depends on the service:

- The YouTube video is age-restricted or for members only. Hamsa can’t fetch it. Upload the audio as a file instead. Private videos and live streams are refused before the job starts.
- “This job can’t run again because some of its settings weren’t saved.” Start the job again from its own page.
A job seems stuck
- A transcript or AI doc stays Pending while it uploads and is processed. Long files take longer. The Activity tray updates on its own.
- A voice over video usually takes 5 to 12 minutes. “Taking longer than usual” appears after 15 minutes on one step, and a render with no progress for 20 minutes stops and shows as failed. Retry it.
- A job that has been running for more than a day is treated as stuck and leaves Running in the tray. Run it again.
Credits and plans
Not enough credits


- The credits are the Owner’s, not the project’s. In a project someone invited you to, your work spends their credits, and their balance is the one that runs out. Calls in Hamsa Agents spend from the same balance.
- Credits expire. Each batch lasts twelve months from the day it arrives. Open Your credits from the meter on Home to see each batch’s expiry date.
- A long job can take the balance below zero. Text to speech checks only that the balance is above zero before it starts. New credits cover the amount below zero first.
”You have reached your speech-to-text usage limit!”
Your plan caps how many transcriptions can be started each month, and you have reached the cap. Text to speech can have a daily cap too (“You have reached your text-to-speech usage limit!”). Wait for the next month (or day), or move to a plan with a higher cap on the Plans tab of Billing.Voices
A voice can’t be used
A voice can’t be added or deleted
Pronunciation
A dictionary word isn’t read right
When dictionaries are on, the words they will change are highlighted in the script. A word you expected to change that isn’t highlighted is the first thing to check. See Dictionaries.
Pages, buttons and permissions
A page or button is missing
An action is refused with “You do not have permission to do this.”
Hamsa Media shows every button to every member. When your role doesn’t allow an action, the request is refused instead. By default, only Owners and Admins add and delete voices and create, change or delete dictionaries. Ask the Owner to give you the permission, or ask an Owner or Admin to do it. See Roles and permissions.I can’t see a teammate’s work
Some lists show only your own work, even in a shared project: text to speech history (a link to someone else’s take opens “Job not found”), voice overs, and web reader sites. Favorites and project defaults are yours too. Ask the teammate to download and share the file. See Concepts.Web reader
The player doesn’t show, or doesn’t play
Other messages readers can see, such as “Article too short”, “No content found” or “Page too large”, are listed in What readers see when something is wrong.
An article plays old text
Hamsa never reads a page again on its own. After you change an article, open it on the Conversions tab and use Clear cached audio. The next play makes it again, and is charged again. See Conversions.Related
Limits
Every number you can run into.
Activity and notifications
Follow jobs and run failed ones again.
Billing
Credits, plans and what to do when you run out.
Roles and permissions
Who can do what in a project.