What is Maximum Attempts for a Test?

The Max Attempts setting allows you to set the maximum number of times a candidate can attempt a test. You can find this in the Main Settings section of your Test Settings.



Let's say you have set Max Attempts as 1. If a candidate tries to attempt the test again (by visiting the same URL), they will see a message like the screenshot below. They will not be allowed to attempt the test again.

What is the Recommended setting for Max Attempts?

Some of you may want to set Max Attempts to a value more than 1 just in case a candidate faces an issue during the test. But, if you are using a Google Form or Socratease Quiz, we highly recommend that you set Max Attempts to 1. This is because AutoProctor automatically resumes these tests. So even if the candidate reloads the page or clicks on the same link, the test can continue.

If you are using Microsoft Forms or IFrame tests, then you may decide the value based on your use case.

FAQs

What if a candidate attempts the test using a different email ID?
If a candidate uses a different email ID, we will not be able to restrict them. For example, say your test attempt URL is Link A. You have set Max Attempts to 1. You share Link A with many candidates. A candidate clicks on Link A, logs in to abc@gmail.com and attempts the test. Then, they log out and log in with xyz@gmail.com and attempt the same test. We will not know that abc@gmail.com and xyz@gmail.com belong to the same candidate. That is, when we say Max Attempts is 1, we mean it is 1 per AutoProctor candidate account.

If you already have a list of email IDs and want to restrict each email ID to only 1 attempt, consider using Email Invitation Links.

I have set Max Attempts as 1 but I see 2 submissions from the same email ID.
This is mostly because the candidate has logged in with different methods using the same email ID. For example, if their email is abc@gmail.com, they could have clicked on Sign in with Google, as well as Sign in with Email. Read this article to learn how to set the Login Methods. Once you restrict the Login Method to a single method, you won't see this issue.

Updated on: 02/03/2025