Troubleshooting + install path

Dropdown not updating?

Google Forms dropdowns do not stay linked to a Sheets range by default. Check the source column, mapping, Preflight result, Update now report, and public respondent preview.

1Sheet column has clean valuessource
2Question is mapped to that columnmapping
3Preflight passes before updatecheck
4Public preview shows new choicesverify

Quick answer

If the dropdown is stale, test one copied form with Alpha/Beta in Sheets, run Preflight, click Update now, then inspect the respondent-facing preview. For automatic updates, run Test scheduled path now and read the per-mapping ledger before repairing or recreating a trigger.

See the scheduled-run and recovery proof

This controlled proof shows the every-6-hour or daily path using the same fail-closed checks, recording mapping-level status, and keeping five bounded recovery versions.

The privacy-enhanced YouTube player loads only after you press play. Controlled copied-form proof with synthetic data.

Complete search tutorial

Fix the failure, then prove scheduled sync and recovery

Follow the copied-form path from source selection and Preflight through exact diff approval, public respondent preview, scheduled-path testing, mapping health, trigger repair, and five bounded recovery versions.

FormSuite Choice Sync refreshes owner-controlled choices before respondents use the form. It is not respondent-time dependent-dropdown, booking, inventory, or payment software.

Triage the failure in order

Do not jump straight to reinstalling. Most stale dropdown cases can be separated into source, mapping, update action, or preview problems.

SymptomLikely causeNext check
Preflight failsFile, tab, column, or question mapping is invalid.Re-select the source and mapped question.
Preflight passes but nothing changesUpdate now was not run, source values are empty, or the wrong form copy is open.Check the update report and form URL.
Editor looks right but public link is stalePreview window is old or the wrong form link is being checked.Open a fresh respondent preview from the tested form.
Only some values appearBlank rows, duplicate cleanup, formula output, or whitespace in the source column.Clean the source column and run one copied-form update again.

Common causes

Source changed

The tab, header, column, blanks, or duplicate values changed after setup.

Question changed

The dropdown was deleted, duplicated, renamed, or changed to another type.

Preview was not refreshed

The editor can mislead you. Open the public form preview after updating.

Header row shifted

Blank or renamed headers can point a mapping at the wrong column. Re-select the column and run Preflight.

No usable values

Empty rows, whitespace-only values, or filtered-out duplicates can leave nothing to update.

Permissions changed

If the selected source file is no longer accessible, select it again from the add-on flow.

If the manual update works but automation does not

Test the exact scheduled path

Choose Every 6 hours or Daily, save, then use Test scheduled path now. A timed run must not bypass routing, quiz, duplicate, type, or 1,000-choice guards.

Read mapping-level health

Check last attempted, updated, skipped, or safe error status for the affected mapping instead of assuming the trigger ran.

Repair before restoring

Verify trigger presence and authorization first. If a bad update occurred, restore only from one of the five bounded versions after live-form safety checks pass.

Screens to compare against

If your setup is stuck before these screens, collect a screenshot of the last screen you reached and send it with the source column and mapped question type.

FormSuite Choice Sync Preflight screen for dropdown update troubleshooting
Preflight should validate the source and mapping before choices are changed.
FormSuite Choice Sync update success screen for Google Forms dropdown
Update now should report a real update. Then check the respondent-facing preview.

FormSuite Choice Sync fix path

1. Use a copied form

Do not troubleshoot directly on a live respondent form.

2. Link one dropdown

Select the spreadsheet, sheet tab, source column, and dropdown question.

3. Prove the result

Preflight must pass, Update now must update, and the public preview must show the new choices.

Migrating from the legacy add-on

Do not repair a live Form Ranger setup in place

If an existing Form Ranger workflow stopped updating or no longer gives you a clear result, copy the form first. Keep the source Sheet unchanged, relink one question in FormSuite Choice Sync, run Preflight, update once, and compare the public preview. FormSuite Choice Sync is an independent FormSuite add-on and is not affiliated with New Visions Cloudlab's Form Ranger.

Use the right tool

Rare change

Manual copy/paste may be enough.

Code-owned workflow

Apps Script works if you maintain IDs, triggers, and authorization.

Sidebar workflow

FormSuite Choice Sync gives a mapped update flow with Preflight, Update now, and a visible result report.

Boundary Do not use a visible dropdown as proof of live inventory, paid booking, or reserved seats.

What support needs to diagnose it

A useful setup-help request should make the failing step obvious. Send the smallest evidence that proves where the chain broke.

Source context

Spreadsheet tab name, source column header, and two visible values from the column.

Mapping context

Mapped question title and type, plus whether the form was copied after setup.

Run context

Preflight result and Update now message, especially whether it says updated, skipped, or error.

Preview context

Whether the public respondent preview shows the old choices, new choices, or a different form.

What not to do first

Do not immediately rebuild the form, reinstall every add-on, or edit the live respondent form while people are using it. First reduce the problem to one copied form and two values. If Alpha and Beta do not update correctly in that copied form, the failing step is easier to find. If the copied form works, the live form likely has a mapping, source, or preview mismatch.

What to capture before asking for help

Source proof

Spreadsheet tab name, source column header, and two visible test values.

Mapping proof

The mapped question type and whether Preflight reports a valid file, tab, column, and question.

Preview proof

A respondent preview check after Update now, not just the editor state.

Next steps

FAQ

Does Google Forms automatically sync dropdowns from Sheets?

No. A Forms dropdown stores choices inside the form.

What should I check first?

Check the source column, mapping, access, Preflight result, Update now action, last update report, and public preview.

Should I fix the live form first?

No. Start with a copied form and two obvious sheet values.

Why did FormRanger say saved but my dropdown did not change?

Saving configuration does not update choices by itself. Run Preflight, click Update now, and then verify the public preview.

Can stale choices come from checking the wrong form?

Yes. Copied forms and duplicated response sheets are common. Confirm the form editor, add-on sidebar, and public preview are all for the same form.

Should I reinstall if the dropdown is stale?

Usually not first. Re-select the source, run Preflight, update one copied form, and only then use support if the result still fails.

What if a scheduled update did not run?

Run the scheduled path test, inspect mapping-level status and trigger health, then repair the configured trigger. Do not recreate triggers blindly or test first on a live routed form.