Not enough credits: what happens and what to do
Credits can run short in two places: before the start and in the middle of work. Before the start, the app simply will not begin and will name the reason. In the middle of work, everything depends on whether the project has local threads. This page covers both places.
Before the start: what blocks the work
The "Start" button opens the "Check before start" window. The "Not ready" section lists the reasons. As long as the list has a money line, the work will not start.
| Window line | When it appears | What to do |
|---|---|---|
| "24.68 credits short of what the start needs" | The reserve is larger than the balance | Top up the balance or shorten the queue |
| "Balance unavailable" | The app does not know the balance | Restart the app or write to support |
| "No credits left" | Periodic run, no local threads | Top up the balance or add local threads |
| "Nothing to run with: no local threads, and not enough credits for the cloud" | Endless run, no local threads | The same |
Under the first line there is an explanation: "The start reserves 98.72 - the most the queue can cost. Balance: 74.00". If copy recreation is on in the project, the text is different: "The start reserves 98.72 - the most the queue can cost, counting recreations (up to 3 attempts). Balance: 74.00".
The money line has a "Top up" button. The lines about the daily video limit have a "Change plan" button.
The reserve is an upper bound, not a bill. The app sets aside as much as the queue would cost in the worst case. So the "credits short of what the start needs" line also appears when less would actually be charged. This is especially noticeable in "Hybrid" mode: the cloud takes a file only when all local threads are busy, and the real amount is not known in advance.
Warnings that do not block the start
These lines are in the "Warnings" section. The "Start now" button works with them.
| Window line | App explanation |
|---|---|
| "Credits are enough for about 12 videos out of 30" | "When credits run out, the cloud threads pause. The local ones keep working. Top up your balance." |
| "Credits are enough for about 12 videos out of 30" without local threads | "There are no local threads - when credits run out, video creation will stop before reaching the target. Top up your balance or add local threads." |
| "The cost is not known in advance: it depends on new videos at your sources" | The material comes from sources after the start |
| "The cost shown covers only the videos already uploaded" | "Credits for videos from sources will be charged on top of that." |
Credits ran out in the middle of work
What happens next depends on whether the project has local threads.
| What is set in the project | Message title | What happens to the queue |
|---|---|---|
| Local threads exist, one-time run | "Credits have run out - the cloud threads have stopped" | The local threads create the remaining videos. The work continues |
| Local threads exist, endless run | "Credits have run out - the cloud threads have stopped" | From then on, only the device creates videos |
| No local threads | "Credits have run out - video creation has stopped" | The work is paused until the balance is topped up |
| Periodic run | "Credits have run out - the cloud threads have stopped" | The current round finishes, and there will be no next round |
The explanation in the first case: "The remaining videos (12) will be created by local threads - slower, but free." In an endless run the text is shorter: "Local threads keep creating videos - slower, but free."
The explanation when there are no local threads: "There are no local threads, and in the cloud every video costs credits. Top up your balance or add local threads."
During the pause, the run bar shows the line "Paused, credits have run out - waiting for a top-up". Next to the notification are the "Top up ↗" button and the "Retry now" button.
How to lift the pause
Follow four steps:
- Press "Top up ↗" next to the pause message.
- Pay for the top-up in the browser.
- Return to the app. The work will continue on its own.
- Press "Retry now" if you do not want to wait. The button contacts the server right away.
The queue is kept during the pause. Finished files stay in place, and nobody counts them again.
What happens to finished videos
The pause does not affect finished files. Everything the app managed to create and download is in the save folder.
A result the cloud managed to produce before the pause is kept in the cloud for a day. You can pick it up manually: the menu button in the header of the main window, the "Global integrations" item, the "VUB Cloud" card, the "Open storage" button. Instructions are on the Cloud storage page.
What was spent and on what is shown in the "Transaction history" window. It opens with the "All transaction history →" link in the balance panel. More about the balance is on the Credits page.
The daily video limit ran out
This is a different limit, and money does not help here. The limit is set by the plan.
The run bar shows the line "Paused, the daily video limit is used up - waiting for the reset". The notification is called "Daily video limit reached". The text: "The work will continue on its own once the limit resets. Change your plan to create more videos a day." Next to it are the "Change plan ↗" and "Retry now" buttons.
In this case the balance panel shows the "Daily video limit reached" bar with the text "Wait a day, or change your plan now and not lose time."
Endless and periodic runs: no price in advance
These runs have no end, so there is no exact amount. The material comes from sources after the start.
The money block in the check window is called "Credit spending". It has the line "The balance lasts about" with a value like "5 passes" or "less than a pass".
The app's exact warning: "Credits are charged for every video created." Then it asks you to keep an eye on the balance. When credits run out, the cloud part of the work pauses. After a top-up it continues on its own.
There is one piece of advice: watch the balance badge at the top of the window. The balance panel shows the "Credits are running out" bar in advance with the text "Enough for about 3 videos in the cloud."
FAQ
Why does the app not let me start even though there are credits on the balance?
The app reserves the worst case, not the average spending. In "Hybrid" mode this is the whole queue. Less is actually charged, but the reserve must be on the balance before the start.
Will I lose finished videos if credits run out?
No. Finished files stay in the save folder. The queue is also kept during the pause.
Can I work with no credits at all?
Yes. "Local" mode spends no credits. It spends the daily video limit the same way as the cloud.
What lifts the pause faster: waiting or the "Retry now" button?
The button. It contacts the server right away. Without it the work also continues on its own, but later.
What happens to the queue if I stop the work myself?
Finished videos stay in the save folder. Files that were not started simply will not go into work. For closing the app, see Connection loss and closing the app.