Troubleshooting autofill failures, incomplete-question blockers, and extension case matching - VisaFlo

Stop before retrying

Do not repeatedly run autofill against a live portal application. First determine whether the issue is source data, case selection, extension support, or the destination portal. Repeating the action without that check can make it harder to see which values changed.

1. Check the source case

Confirm that you opened the correct VisaFlo case and that its client, case type, and family-member information match the intended portal application. Review required questionnaire sections and visible validation messages. A completion percentage alone does not prove that the data needed for portal entry exists.

2. Check the extension and portal state

Confirm that the installed extension supports the portal and application type you are using. Make sure the extension is enabled, the target portal is open to the correct application, and you are signed in with the authorized account. Do not switch to another client or portal record while the extension is working.

3. Check the destination fields

If the action runs but a field is blank or incorrect, compare it with the related questionnaire answer and source document. Correct the source record, then retry only the relevant workflow. Fields that depend on professional judgment, a portal-specific choice, or unsupported data may require manual completion.

Common symptoms

Symptom	Check first
Autofill action is unavailable	Case type, questionnaire requirements, and extension support.
A required field is blank	The related answer, validation, and whether the field is supported.
Data appears in the wrong portal record	Client, case, and portal application identifiers.
The portal layout does not react	Extension version, portal changes, and browser extensions that interfere.
The output looks stale	Whether the source questionnaire changed after the previous run.

Escalate with a safe reproduction record

When you contact support, provide the case type, VisaFlo case ID, portal step, action taken, visible error, browser version, and whether the issue reproduces on a synthetic or non-sensitive test case. Do not send portal passwords, access tokens, or full client documents. See Autofill with Extension and Automation & Review.