All 19 Cookie Consent sections
Asking again
Somebody who has answered is not asked again until their answer runs out (Settings → Remember an answer for), with two exceptions.
When the banner asks about a new kind of cookie. If your site starts using a kind it did not use before (say a reading finds an advertising pixel a plugin has added, or you add a rule of your own for Advertising), everybody who answered before that is asked again on their next visit. The banner opens with the choices showing, what they agreed to before is still ticked, and the new kind is unticked with a small New tag. What they agreed to before goes on running while they decide; the new kind waits for their answer, even when an answer from long ago once allowed it. Taking a kind away never asks anybody again. On a shop, the first reading after updating to this version usually adds Advertising, for WooCommerce's order attribution, so visitors who answered before are asked once more then. If you have switched on Treat scrolling as agreement, scrolling on while the banner asks about the new kind agrees to the new kind only: what they refused before stays refused.
When you press Ask everybody again. Settings → How it asks → Ask everybody again. You are asked to confirm first, because it cannot be taken back, and nothing happens until you do: opening it in a new tab or with the middle mouse button does nothing, and so does an old link or bookmark to it, which, opened while you are signed in, brings Settings back with a note saying nobody was asked again. If you have changed anything else on Settings and not saved it, you are then asked whether to go on without saving, because Settings comes back as it was stored. The same question is asked on Settings, The banner and What is held back when you move to another of the plugin's screens (with its menu, or with Back or Forward between them), or send another form on the screen, such as Import, with changes you have not saved. Saving, or exporting a settings file, asks nothing. Leaving the plugin's screens altogether, or closing the tab, is left to your browser, as on WordPress's own settings screens. Everybody who has answered sees the banner on their next visit, exactly as on a first visit: nothing ticked, nothing held back is put back, and other plugins are told nothing is agreed (see Other plugins on your site) until they answer. Your page cache is emptied, so the change reaches cached pages. The screen says when you last pressed it. It is for when you have changed what you do with visitors' data and want everybody to decide again. It is not carried in the settings file, so pressing it on a staging site never asks the visitors of your live site.
When somebody would be asked again but their browser refuses tracking (Global Privacy Control or Do Not Track), they are not shown the banner: the refusal is written as their new answer, and recorded. Where you ask only in some places (Who is asked), a visitor who is not asked where they are keeps their earlier answer.
Answers given before this version are still answers after you update: nobody is asked again because of the update itself, with one exception. On a network set up with sub-directories, whose sites share one address (see Multisite), each site now keeps its own answer, so visitors who answered there before are asked once more on each site. The kinds your banner asked about on the day you update are noted on the first request after it, whichever page that is, so a reading you make straight after updating still asks those visitors about anything it adds. A cache the plugin cannot empty goes on serving the old page, and so not asking again, until it expires.
Still stuck? Ask the developers who wrote it. We aim to reply within one business day.