The confirmation button stays frozen

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

The causes, from the most common to the rarest

1. 1

   The delay has not yet elapsed on the server side

   The display sometimes runs a second ahead of the server. The button unlocks as soon as the server judges the delay to be over, never a moment earlier.

2. 2

   The page was reloaded

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

3. 3

   The authorisation has expired

   A confirmation left open too long eventually expires. You then have to start over 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 cannot 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

   This is the most common and most harmful move: it erases the waiting time already elapsed.

3. 3

   Start again from the form if the authorisation has expired

   Begin again from the home page rather than reusing a tab that has stayed open too long.

4. 4

   Accept the cookies placed by the site

   This cookie only serves to carry the send authorisation; without it, the confirmation cannot succeed.

Commonly asked questions