Video service unavailable or slow
What to do when the video service is not responding, starts slowly, refuses a request under heavy load or when your session has expired, and where to check it.
Every Clipfer render goes through the online video service, which works inside your private space. It sometimes starts slowly, gets saturated for a few dozen seconds, or refuses a request because your session has expired. In almost every case, the Studio retries on its own and nothing is lost. Here is how to read each message.
The service connection messages
When a tool needs the service, a banner shows its state:
| Message | What is happening | What to do |
|---|---|---|
| Connecting to the video service… | A check is running. | Nothing: a few seconds. |
| The video service is starting, a few more seconds… | An instance is waking up; normal after a quiet period. | Wait. |
| Video service ready | All is well. | Start the job. |
| The video service isn't responding right now. Retrying automatically in a few seconds: nothing is lost. | The service is unreachable or briefly down. The Studio retries every fifteen seconds. | Wait, or click Try again. |
| The video service is answering, but its processing tools aren't ready. | The instance is up but not operational yet. | Automatic retry. |
| Your session has expired: sign in again to keep using the video service. | Your account session is no longer valid. | Click Sign in again, then resume. |
Until the banner reads Video service ready, the launch buttons stay blocked with a message such as The video service is not ready: rendering cannot start.
Under heavy load: the queue and passing refusals
When many renders run at the same time, two things can happen:
- Your render is queued: the tool shows Waiting in the service queue · N (or Queued at the service (N)). It starts as soon as a slot frees up.
- The host has no free instance at that instant and refuses the request with a 429 "no available instance" error. It is not an answer from the service: nothing was done. The Studio retries automatically several times, over about thirty seconds in all, while a render frees the slot. You usually only see the wait.
If every retry fails, the file goes to Failed and the Retry the failures button picks it up again. A paid render that fails is refunded.
The same applies to transcription and analysis: Too many transcription requests at once. Try again in a moment., Too many analysis requests. Try again in a moment. or The analysis model is not responding right now. are passing refusals, retried twice automatically before being reported.
Expired session
A session expires after a long idle period, or if Remember me was not ticked and the browser was closed. The messages Session expired: sign in again to run the analysis. or Your session has expired tell you so. Sign in again: your batches and settings are still there, and a job already running on the service keeps going.
Checking the service state
The round button at the bottom right of the Studio opens the Clipfer support panel. Its Service status entry checks two things: Video service and Database and accounts, each marked Operational or Unavailable, with the measured response time; Check again reruns the check.
What not to do
- Do not reload the page during a render to "speed it up": the job follows your tab, and a page closed before the end leaves an Interrupted project in My projects (files already produced are kept).
If nothing comes back
After several minutes without Video service ready, or if the same file fails three times in a row, contact support from the panel at the bottom right, with the tool name, the time and the message shown. The credits of a render that did not go through are already refunded; check it in the Credit usage history on the Subscription page.