Choice Eliminator not working: five causes and what to do
When Choice Eliminator (or one of its many clones) stops hiding full options, it is almost always one of five things: the add-on could not be installed or vanished from the form, the trigger that does the work did not run or ran late, the counts reset after you edited an option's text, "go to section based on answer" branching paused the elimination, or you copied the form and the copy has no triggers. Each one has a fix below. At the end is the case that is not a bug at all: two people submitting for the last seat in the same moment, which no trigger-based add-on can stop.
"Choice Eliminator" is a family now, not one product. The original Choice Eliminator 2 was copied many times, and most searches for it land on Choice Eliminator Lite, Choice Eliminator 3, CAPY, Skyfield's Form Limiter or Everest's Form Choice Limiter. They all run on Google Apps Script triggers, so they fail in the same ways. I installed each of them in July 2026.
1. The add-on could not be installed, or it disappeared
If the one you are trying to install is Choice Eliminator Lite (Accemy & SW gApps), stop there. It has 2.89M+ installs and about 3 stars, and when I tested it in July 2026 the install did not go through at all. Its own developer describes it as a tool for light use. If it was working on your form and has now gone from the Add-ons menu, same story.
The fix is a different add-on. Open the puzzle icon, choose "Manage add-ons", and remove the one that is not responding before you install the next. Within the trigger-based group, Form Limiter (Skyfield) (1M+ installs, 4.91 stars) has the cleanest permissions. Choice Eliminator 3 asks to see, edit, create and delete all your Google Sheets and every form in Drive, which I would not grant for a sign-up sheet. I compare five of them in the choice eliminator comparison.
2. The trigger did not run, or ran late
This is the one behind "it still shows full options". All of these add-ons work the same way. A response lands in Google Forms. Then an Apps Script trigger wakes up, counts the responses, and edits the question to remove the option. The check happens after the response is already stored. If the trigger is slow, the option stays visible for minutes. If the trigger fails, it stays up until you notice.
Triggers fail for dull reasons. Apps Script has daily quotas on trigger runtime, and a busy form can run into them. The owner's account has to stay authorized to "run when you are not present", and a password change or a school admin's policy can revoke that. And there is a hard ceiling: Apps Script allows 20 triggers per account for a script, which for Form Limiter (Skyfield) works out to about 10 limited forms per Google account. The eleventh form installs fine and never eliminates anything.
The fix: open the add-on's sidebar on the affected form and run its setup or "activate" step again, which re-creates the trigger. Retire the limited forms on the same account that you no longer need. If the form is popular, warn respondents in the description that a full option can stay visible for a minute or two.
3. The option came back, or the count reset, after you edited the text
Form Choice Limiter (Everest Web Deals) (1M+ installs, 4.86 stars) keeps each count keyed to the option's text. Fix a typo in "Tuesday 4pm" on a live form and the add-on sees a brand-new option with zero bookings, so it reappears with full capacity. The reverse bites too: two options with identical text share one count, and both can overbook.
The fix is to leave option text alone while the form is live. If you have to change it, close the form, edit, then reset that option's limit in the sidebar to the seats that are really left. And give every option unique text, even if that means "Tuesday 4pm (Room A)" and "Tuesday 4pm (Room B)".
4. "Go to section based on answer" paused the elimination
If the limited question routes people to different sections depending on their answer, removing an option takes the routing with it. Skyfield's Form Limiter handles this by auto-pausing elimination on any question with branching. Everest's FAQ admits that removing options breaks "go to section" routing. Either way the full option stays visible, by design.
Within these add-ons, the fix is to split the question: limit a plain question with no branching and route from a separate one. Or use an add-on that keeps the routing when an option is hidden (last section).
5. The form was copied and the copy has no triggers
Make a copy of last term's form and the questions come along, and so does the add-on's entry in the menu. The triggers do not. They belong to the original form, so the copy looks configured in the sidebar and nothing fires. This is the cause I see most often on recurring forms, and the cheapest to fix: open the add-on on the copy and run its setup again. Check the trigger count first (cause 2), because the copy needs a fresh set.
When it is not a bug: two submits on the last seat
This is the one no amount of re-running will fix. Two parents open the form at 7:59 for an 8:00 release and both submit for the last seat inside the same second. Both responses are stored before any trigger runs, so both get through, and the add-on removes the option afterwards. Skyfield's reviews mention 1 or 2 responses over capacity on busy forms, and the same thing happens with every tool in this family. It is the design, not a defect.
The only real fix is to decide who gets the seat before anyone is told they have it, which means a server-side tool rather than a trigger. That is why I built Form Slots. It is a Google Forms add-on like the others, but bookings are decided on its own server, one at a time per form (a Firestore transaction), so two people who submit in the same second cannot both get the last seat. There are no Apps Script triggers, so causes 2 and 5 do not exist: nothing to re-activate, no 20-trigger ceiling, no "run when you are not present" permission to lapse. Routing keeps working when an option is hidden, so cause 4 goes away too. The form stays on its normal link and QR code.
Setup takes about a minute:
- Add-ons (puzzle icon) > Form Slots > Configure slots.
- Pick the question and type a capacity per option. "Set all slots to" does them at once.
- Save & activate.
A full option is removed from the live form usually within a minute, and it comes back if you delete a response or raise the limit. Turn on Settings > "Collect email addresses" and extra sign-ups go to a waitlist and are promoted automatically (how the waitlist works). Free is one live form at a time with every feature. Pro is $6/month or $49/year for unlimited live forms. Form Slots is new, so there is no install count to put next to the add-ons above.
Before you switch tools
Run through the five causes in order. Most "not working" reports end at cause 2 or 5, and both are fixed by running setup again. If the overbooking is always exactly 1 or 2 on the busiest slot, you have hit the trigger design limit. For every other way to cap a form, native settings included, see how to limit responses in Google Forms.
Questions people ask
Why does Choice Eliminator still show options that are full?
Every add-on in this family runs on an Apps Script trigger that fires after the response is saved. If the trigger is slow, quota-limited, or was never created, the option stays visible. Re-run the add-on's setup on that form.
Can Choice Eliminator overbook a slot?
Yes. Two submissions in the same second are both stored before the trigger runs, so busy slots can end up 1 or 2 over capacity. Skyfield's reviews mention it. Only a tool that decides each booking on its own server, one at a time, avoids this.
Why can't I install Choice Eliminator Lite?
When I tested it in July 2026 the install did not go through. Its developer describes it as a tool for light use. Pick another add-on from the same family instead.
Does Choice Eliminator work with 'go to section based on answer'?
Not reliably. Form Limiter (Skyfield) pauses elimination on questions with branching, and Everest's FAQ says removing options breaks the routing. Form Slots keeps the routing when an option is hidden.
Do I have to set the add-on up again after copying a form?
Yes. A copied form carries the questions but not the triggers, so the sidebar looks configured and nothing fires. Open the add-on on the copy and run its setup again.