When something goes wrong
The failures you are most likely to hit in a project, what each one actually means, and what to do about it.
Most of these look alarming and are not. The important thing in every case is that your files are not at risk - a failed run, a failed push and a conflict all leave your code exactly where it was.
"File changed elsewhere"#
The stored copy of a file moved while you had it open - another tab, another device, or an import that touched it.
You are shown both versions side by side, yours and the stored one, and you choose. Nothing is written until you do, and nothing is silently merged.
The related case is "File deleted elsewhere" - the file is gone from storage but still open in your editor. Save it to bring it back, or close the tab to let it go.
A run is refused before it starts#
- A file is over the run ceiling. Files can be stored at 100 KiB but only run at 64 KiB, and the message names the file. Shrink or remove it. See project limits.
- Too many files. The sandbox takes 60.
- The runner is unavailable. A separate service, and it can be down. Try again shortly; nothing about your project is wrong.
The program compiled but printed nothing#
Usually one of:
- Run executed a different file than you expected. It follows the file you are looking at - check the tab in front. Running your code.
- It is waiting on input that never came. Everything is delivered up front from the Input tab, so a program expecting more than you supplied reaches end-of-input.
- It genuinely printed nothing, which for a class with no
mainis exactly what a runtime says in its own words.
A push fails or looks wrong#
- "GitHub has commits this project doesn't" - the repository moved on. Do not push over it without reading the review first.
- "Too large to compare" - no change set can be shown, so a push sends everything.
Pushing to GitHub covers both.
The assistant charged me and I rejected the answer#
That is intended. You paid for a generation and received one; rejecting is a judgement about the output, not a fault. Refunding rejections would make repeated generation free.
The quote is shown before you confirm, and a repeat of the same question is free from cache. See AI assist.
Something is genuinely broken#
If a failure does not match anything here - especially anything that loses work or shows you somebody else's data - tell support with the project name and roughly when it happened.
Was this page helpful?