Note: Articles in languages other than English are translated with the help of AI. While we aim for accuracy, some wording may vary slightly. If you notice anything that could be improved, we'd love to hear your feedback.
Problem:
Sometimes when working on an exercise, your session may disconnect unexpectedly. Here is a quick troubleshooting guide to help you resolve this.
Step 1: Identify when the disconnection occurs
The first thing to determine is whether the session disconnects before or after submitting your code.
Session disconnects after submitting code
If the session disconnects after you submit your code, the most likely cause is a syntax error that is causing the session to crash. This may also appear as an error alert stating:
"The code took too long to execute."
How to troubleshoot:
- Use the Hint option or view the Solution code to compare it against the code you submitted.
- Look for differences between your code and the expected solution.
.
- If the difference is not easy to spot, consider using a third-party tool such as Diff Checker to help identify discrepancies.
-
Once you have adjusted your code or replaced it with the solution code, run the code and submit again, by hitting "Run Solution" — this should fix it and allow you to continue to the next exercise!
Session disconnects before submitting code, or persists after adjusting it
If the session keeps disconnecting before you do anything, or continues after you have already adjusted your code, try the following standard troubleshooting steps:
- Clear your browser's cookies and cache.
- Open an incognito or private browsing window and try again.
- Try a different browser to check whether the issue persists across multiple browsers.
- If the problem continues, contact our support team and include the exercise URL — we'll be happy to help.
For projects, we have recommended troubleshooting steps; for starters, we recommend saving your code and resetting the project.