We know that a browser crash—especially a memory-related issue on a device like a Chromebook—is the last thing any student wants to deal with during an important test or assignment.
We’ve designed our online assessment system with a robust, multi-layered data saving architecture to make sure that a client-side crash results in minimal, if any, lost work. The result? At worst, you might lose only the last few seconds of work on the single question you were answering.
Here’s a look at how our system ensures maximum resilience against unexpected interruptions.
1. Answers Save Instantly (Per-Question Saving)
We don’t rely on a single “Save” button or a large, infrequent auto-save. Instead, we use a technique called asynchronous saving that pushes your answers to our secure server the moment you make a change.
- Multiple-Choice & True/False: As soon as you click an option, that selection is immediately sent to the server and recorded. Data loss for these question types is virtually impossible unless the crash occurs mid-click.
- Short Answer & Essay: When you are typing, your response is saved frequently and on critical events (like clicking out of the answer box). This means the work you’ve completed on previous questions is secure, and only the latest few seconds of typing on the current question might be lost if the crash happens before the final save request completes.
2. Time Used is Tracked and Recovered
For timed assessments, losing time due to a crash is just as frustrating as losing answers. Our system actively tracks and saves your elapsed test time to ensure a fair recovery.
- Periodic Time Logging: A small, background function logs the total minutes you’ve used to the server at regular, short intervals.
- Seamless Resumption: If your browser crashes, simply closing the crashed tab or restarting your device and logging back in will resume your test. The system immediately retrieves your last logged time, deducts it from your original limit, and starts the countdown from your remaining time. You will see a “Resuming” message before you continue.
3. What Isn’t Saved (And Why It Doesn’t Matter)
While core data like answers and time are continuously saved, some non-critical, client-side items might be lost:
- “Mark for Review” Status: Any questions you had flagged for later review will need to be re-marked upon logging back in.
- Window State: Settings like “full-screen mode” will revert to default and will need to be re-initiated.
These minor losses have no bearing on your score or the integrity of the test. Our priority is making sure the data that counts—your answers and your remaining time—is secure and waiting for you when you log back in.