Message: Video generation timed out¶
What this message actually means¶
When you see a message like:
“Video generation timed out after 60 attempts (10 minutes). The operation may still be running on Google's servers.”
it can feel like something failed. But in reality, this message is a bit misleading.
Nothing actually broke.
What happened is much simpler: Craftology stopped waiting for a response.
What’s happening behind the scenes¶
When you generate a video, Craftology sends your request to an external model (for example, Google’s Veo). From that point on, Craftology waits for the model to return a result.
However, this waiting is not infinite.
After about 10 minutes, Craftology stops checking for updates and shows a timeout message. This is just a time limit, not a failure.
Note
The video generation may still be running on the provider’s side — even after you see the timeout.
In other words, the system stopped watching, but the process might still be continuing in the background.
What you should do next¶
Give it a bit more time¶
In many cases, the video finishes shortly after the timeout.
Wait a few minutes and then check again. It’s common for results to appear with a slight delay.
Check if the result is already there¶
Before trying again, take a moment to look around:
- Scroll through the chat outputs
- Check the shot’s video results
- Refresh the page
Sometimes the video has already been generated — it just hasn’t appeared yet in the interface.
Tip
A simple refresh often resolves this.
Try generating again¶
If nothing appears after waiting and refreshing, you can safely run the generation again.
Start by retrying without changing anything. This helps confirm whether the issue was just a temporary delay.
If it keeps happening¶
If you see this error repeatedly, it usually means the request is too heavy or complex for the time limit.
You can improve success by simplifying the task:
- Shorten the video duration
- Lower the resolution
- Reduce motion complexity
- Use fewer or simpler references
These changes help the model finish faster and avoid hitting the timeout window.
Avoid running too many tasks at once¶
If multiple generations are running at the same time, they may compete for resources.
This can slow everything down and increase the chance of timeouts.
Tip
For best results, run one heavy generation at a time.
When to contact support¶
Occasional timeouts are normal. But you should reach out if:
- The same request fails repeatedly
- Even simple prompts consistently time out
- No results ever appear, even after waiting and refreshing
These cases may indicate a deeper issue.
Review the Reporting an Issue topic for more information.