My terminal or code editor does not load, is very slow or stops responding during the lab

In short

Under heavy load or network latency on our side, the technical environment takes 30 seconds to 1 minute to restart. Your assessment timer keeps running during that time; 5 extra minutes are always added to the lab duration to cover this kind of latency. Refresh the page, then close and reopen the lab window from your invitation link: your attempt and your work are kept. Contact Scalyz Support from the ? Help button if the terminal or editor still does not respond after 3 minutes, without waiting for your time to run out. After 5 minutes without an environment, stop trying to continue the lab: report the problem and wait for our reply.

What to do

1. Leave the page open for 1 minute. The environment restarts on its own within 30 seconds to 1 minute.
2. Refresh the page (F5). This does not create a new attempt and does not delete your work.
3. If nothing changes, close the lab window, then reopen your assessment from the link in your invitation email. You get your attempt and your work back as long as the assessment is still in progress.
4. If you switch browsers, do it the same way: open the link from your invitation email in the new browser. The link signs you in directly, with no password. The timer keeps running while you do this.
5. If the terminal or editor still does not respond 3 minutes after the problem started, contact Scalyz Support from the ? Help button right away (see below).
6. If the environment is still not back 5 minutes after the problem started, stop the lab: do not try to continue and do not repeat the steps above. The 5-minute margin planned for latency is used up; Support takes over.

What you should see

The terminal accepts your commands without delay and the code editor shows your files.

Good to know

• The timer does not stop during the problem, nor while you switch browsers. Do not spend your allotted time retrying: contact Support once 3 minutes have passed.
• The lab duration always includes 5 extra minutes to cover possible latency. Beyond 5 minutes of blockage, a fair assessment between candidates is no longer possible on this attempt: that is why we ask you to stop and report the problem.
• After analysis and validation of your report, Scalyz Support sends you a new assessment invitation and informs your recruiter itself.
• Refreshing the page, closing the window or switching browsers does not create a new attempt and does not delete your work, as long as your assessment is in progress (not expired, not finished). Your files stay in the environment until your allotted time ends.
• Your invitation link signs you in directly: there is no account and no password to enter to get back into your lab.
• The assessment runs on a computer with Firefox, Chrome, Microsoft Edge, Safari or Opera. It is not supported on tablets or phones.
• Turn off ad blockers (AdBlock…), accept cookies and use a stable internet connection.
• On a work computer, security software can block access to the assessment environment. Check with your administrator that you are allowed to share information with Scalyz Support for troubleshooting.
• On a personal computer connected to a company network, the network's security equipment can also block access. Use a personal network if you can, or ask your network administrator for permission to share information with Scalyz Support.
• If it is your own internet connection that dropped, see the article "I lost my connection or got disconnected during the assessment".

When to contact Scalyz Support

If the terminal or code editor still does not respond 3 minutes after the problem started, contact Scalyz Support from the ? Help button. If the blockage goes beyond 5 minutes, stop the lab and report it immediately the same way. If your time has already run out, contact Scalyz Support from the help bubble in your Scalyz space.

The state of your environment is attached to your request automatically. Support replies within 4 working hours, 9am to 6pm Paris time. If a problem on our side stopped you from continuing, this attempt is not held against you and you receive new access. There is nothing to report to your recruiter.

What to include

• What you observed (blank terminal, endless loading, lost connection, commands with no response, slowness) and the time the problem started.
• Your browser, and whether you are using a work computer or a company network.
• If you can, a screenshot of the problem.
• If you can, the errors from the browser console: right-click the page, Inspect, Console tab. Take a screenshot or copy and paste the errors directly into the conversation with Support. In the Network tab, a screenshot of the failed requests (shown in red) also helps.
• How you prefer to be contacted: by email, or by phone with your number.