The Max redirects per visitor setting determines how many times a visitor can be redirected from the waiting room to the protected site when their turn comes.
If a visitor exceeds this limit, they will be redirected to the Max Redirects Exceeded error 5 page.
This article explains:
Max redirects per visitor setting
In a perfect network, each request for a web page or resource would work the first time, every time. Unfortunately, due to traffic congestion, wifi connections, user behaviour, etc, pages do not always load on the first or even second request. For this reason, each waiting room has a Manage > Waiting Rooms > Display > Max redirects per visitor setting. It is set to a default value of 3 to allow a visitor's browser to request the protected page multiple times, when their turn comes, in case the first few times fail.
The problem with increasing this value is that some visitors will abuse the Queue-it system and reuse the url so that they or other people can open extra sessions on the protected site. The url takes the form of https://yourprotectedpage.com/?queueittoken=abcxyz...
The url is available from:
the Network tab in your browser's Developer Tools
the Queue-it email notification
the Queue ID link in the waiting room
the link in the "It's your turn" pop up.
Error Pages
After this redirect limit is exceeded (i.e. by default on the 4th attempt), they will be sent to the Max Redirects Exceeded error 5 page. To identify which error page it is, look at the url. It will take the form https://
.queue-it.net/error?er=5&c=
&e=
The error page can have 2 headings: "Used queue number" or "Rejected queue number". "Used queue number" is displayed when the Max Redirects is exceeded after 30 seconds. The "Rejected queue number" is displayed when the Max Redirects is exceeded within 30 seconds. Both urls are the same. If visitors see the "Used queue numbers" page, it is more likely due to abuse, while the "Rejected queue numbers" page more likely suggests an integration error.
See section 5.5.2 Error Pages of the Technical Integration White Paper for more information.
Are these errors a concern?
If Max redirects per visitor is set to the default of 3, Exceeded Max Redirects should be less than 10% of your Queue Outflow. A figure greater than 10% suggests that there is an implementation error and you should contact Queue-it Support.
Some Connectors face this problem more than others. CDN Connectors see this problem the least, because they are most performant and Connector code is isolated from application logic. Server-side Connectors can see higher max redirect numbers because requests still hit the application and the Connector code can be inserted in to the application in many different ways. Finally, client-side JavaScript implementations see the most errors because the first page must still be loaded before visitors are sent to the waiting room.
Often the best solution is to change to a server-side or CDN Connector.
Checking your traffic
The first place to check is the Diagnostics tab of your Monitor page. Here you will see your Exceeded Max Redirects.
Exceeded Max Redirects only occur when there is traffic leaving your waiting room. It does not happen during Safetynet Outflow. Therefore, calculate it as a percentage of your Queue Outflow, which you can find in the Monitor > Queue tab.
The second statistic to look at is Fast Re-Enters. This is the number of visitors who get another place in the waiting room within 30 seconds of their first redirect to the protected page. A high fast re-enter number suggests problems with implementation. This can also be caused by Queue-it cookies not being saved by the browser.
Statistics > Graphs can show you Rejected: Too many redirects and Fast re-enters over time and in relation to Waiting room outflow.
If you have Premium Reporting, you can export your waiting room data to csv file from Statistics > Export Waiting Room Data. This csv file contains Queue IDs and Number of Redirects, as well as other data, which allows you to analyse specific traffic.
What causes max redirect exceeded?
The following are possible causes of max redirect exceeded and error 5 pages:
implementation problem
queueitAccepted cookie not being saved due to browser setting
visitors reloading the redirect link too many times, either to abuse the feature or due to the protected page not loading quickly enough.
How to reduce Max Redirect Errors
If the error is caused by your site not responding quickly enough, visitors will click the "your turn" link more often. The following solutions improve site responsiveness and discourage multiple clicks:
reduce the max outflow to reduce load on the site.
share links to specific product pages in the email notification or waiting room. This reduces navigation and time on your site and thus makes it more responsive. With Custom Themes it is also possible to create a product page selector with JavaScript. This allows customers to choose the page they wish to go to before it is their turn.
monitor the Exceeded Max Redirects statistic during the event and calculate it as a percentage of Queue Outflow.
if possible, switch to a server-side or CDN Connector.
remind customers in the waiting room and in email notifications (if enabled):
to only click the "It's your turn" link once and explain that they will lose their turn if they click too many times.
to use only 1 browser tab for their entire journey, even if they get the email notification on a different device.
to allow cookies on their browser.
to use a stable internet connection.
not to use the back button to return to the waiting room, if you are using the client-side JavaScript Connector.
Only increasing the Max redirect per visitor setting or setting it too high can increase traffic to your site so an appropriate balance should be determined.
If you do face a high Max Redirects, you can use Custom Themes or dynamic messages to communicate with customers in the waiting room.
Related Information