The confirmation button stays frozen

The 60 seconds preceding each send are measured by the server, not by your browser. That's what guarantees their reliability, but it's also what explains the cases where the button seems stuck: your screen shows a counter, yet it's the server that decides.

The causes, from the most common to the rarest

1. 1

   The delay hasn't yet elapsed server-side

   The display has sometimes gotten a second ahead of the server. The button unblocks as soon as the server judges the delay has passed, never a moment sooner.

2. 2

   The page was reloaded

   Refreshing speeds up nothing and can cancel the current authorisation. The counter then restarts from zero on a new request.

3. 3

   The authorisation has expired

   A confirmation left open too long ends up expiring. You then have to start everything again from the form.

4. 4

   Cookies are refused

   The authorisation travels through a signed cookie. If your browser blocks the site's cookies, the server can't link your request to your session.

Steps to follow

1. 1

   Allow a few extra seconds

   Leave the page open without touching it: the button activates on its own once the real delay is reached.

2. 2

   Avoid reloading the page

   It's the most common and most harmful action: it erases the waiting time already elapsed.

3. 3

   Start over from the form if the authorisation has expired

   Begin again from the home page rather than reusing a tab left open too long.

4. 4

   Accept the cookies set by the site

   This cookie only serves to carry the sending authorisation; without it, the confirmation can't succeed.

Frequently asked questions