This guide is intended to help interviewers troubleshoot problems with CodeCollab and collect information that would help the Byteboard team debug issues. Below is a recap of the two most common issues:
IDE session becomes unresponsive
- If the session has become unresponsive only for the interviewer but not the candidate, it could be the result of a network disruption. As long as the candidate’s connection is active and functional, the interviewer should be able to simply refresh their page to reconnect or rejoin the session. In these scenarios, the candidate might see an error like this:
- If the candidate sees the following error, the session is likely still be active despite the misleading error. The interviewer and candidate should both try refreshing the page and the session should reactivate.
- In the event that the session stops responding for both the candidate and the interviewer and refreshing the page does not help, we recommend restarting the session. This will create new links for both the candidate and interviewer and any progress the candidate has made on their code should be copied over to the new session.
- If a session crashes or becomes totally unresponsive, please report the issue to the Byteboard team. We’d love if you could provide any of the following information:
- What behavior did you observe before the session ended? Were there any network disruptions? Was the session unresponsive for the interviewer or candidate first? Were there any error dialogs? If so, please provide screenshots.
- What date & time did the interview occur?
- If possible, please provide a screenshot of any debug logs that appear in the Output view from the Candidate’s IDE:
Interviewer can’t join session
We have gotten occasional reports that the Join Now button is not enabled properly for interviewers. This can be resolved by simply refreshing the page or opening the ide.byteboard.dev link in an incognito window.
