Skip to content
Flux Forms

Home / Troubleshooting

Messages explained

The messages you are most likely to hit, and what each one actually means.

Access and permissions

"You don't have access to a field / can't see submissions." Your role controls this. Marketeers have no submission access; analysts have read-only submission access. Only administrators can edit them. Ask your admin if your assignment is wrong. See Getting access.

"I can't change a required field as an Analyst." Analysts are read-only by design. Required fields are visible but not editable for you.

Saving

"Nothing happens when I save a form with an empty name." A form must have a name — the Label is required. Save is blocked with an inline message. Type a name to continue.

"Duplicate value found on Form Key." Form Keys are unique across the org. Pick a different one.

Save rejected, naming a field. The form writes or reads a Salesforce field its Purposes do not grant. Edit access is needed for a submission action, read access for a data mapping. Have an administrator add the field to a purpose, assign that purpose to the form, then save again. A form with no purposes assigned cannot save any Salesforce field reference at all. See Saving.

Pickers that look empty

"The section image picker says 'No images available…'." The picker only shows images from a CMS workspace you are a member of. General Salesforce CMS access is not enough — ask your admin to add you to the specific workspace, for example as a Contributor.

The same message appears if Salesforce CMS is not set up, the workspace has no images, or the Workspace Id is missing from CMS Media Settings. See Section images.

Data Mapping offers no source objects. No purpose grants read access. See Assign purposes.

Submission Actions offers no objects or fields. No purpose grants edit access. Same fix.

Invoke flow shows no flows, or the field is hidden entirely. The form is unsaved, has no purpose, or its purposes whitelist no flows. An administrator whitelists flows per purpose in the Purpose Manager. See Whitelist flows.

"No Apex handlers are approved for this form yet." The Run Apex action has nothing to offer: the form's purposes approve no Apex classes. An administrator approves them per purpose. See Approve Apex handlers.

The Apex handler picker in Purpose Manager is empty, and names an interface. No class in the org implements fluxforms.SubmitActionApexHandler — or, far more often, one does but was written public instead of global. A public class compiles and is then invisible to Flux Forms, with nothing on screen to say why. Class, both methods, and an explicit no-argument constructor all have to be global.

Apex and on-demand flows

"This is an on-demand flow, which cannot be started directly. Register an Apex handler in Flux Forms Setup to run it." Shown when whitelisting. You can still whitelist the flow — it just cannot run until an administrator registers the proxy class in Apex Handler Settings. See Apex Handler Settings.

A flow row shows the status "Needs Apex handler". Same cause, seen from the purpose's flow list. It flags exactly which entries cannot run yet, does not block anything, and clears on its own once a handler is registered.

A submitted form records an Error naming Flux Forms Setup > Apex Handler Settings. The action needed the proxy and it is missing or switched off. Check that a Flow proxy class is set and Handler active is ticked.

The proxy is registered and active, but the on-demand flow still errors. The step everyone misses: the background Automated Process user needs Flow Access on that specific flow, granted through a permission set. The org-wide "Run Flows" permission is not a substitute.

Saving the flow proxy class is refused. The class name is validated before it is stored, so a class that has been deleted or renamed is rejected at save time rather than failing later during someone's submission.

Save rejected, naming an Apex class. The form has a Run Apex action pointing at a class its purposes do not approve. Have an administrator approve it, or remove the action.

A packaged flow starts the wrong thing, or nothing. It was whitelisted before version 0.8.0, when package prefixes were not recorded. Remove it and add it again from the picker. Your own org's flows are unaffected.

Publishing

Activate is disabled. Either the form has health errors — the button tells you how many — or it has no saved configuration. See Form health.

Open Form is disabled. The form is not Active, or the Site Base URL is not configured. See Open the live form.

The published form

The public site showing an unavailable message for a form key that does not resolve

Visitors see a placeholder instead of my section image. The image is picked, but the CMS workspace is not published to a public delivery channel, or the image is not published to it. The builder showing the image is not evidence the public form will.

A visitor's link says the form is unavailable. The form is not Active. Deactivating takes a form offline immediately.

My old prefill link stopped working. Links using ?form=<id>, a raw record id such as ?leadId=00Q…, or ?<field key>=value were removed. Regenerate with the Build Flux Forms Prefill Link action. See Prefill links.

A prefilled link loads the form empty. The token is tampered with, expired, or being used on a different form. Prefill fails closed — the form still loads, just without the values.

Rules that do not fire

My field never appears, even though the rule is right. The field is probably visible by default. To make a field appear only under a condition, check its Hidden toggle in the Fields scope and add a Shown rule. See Field types.

Two rules fight over the same field. The lower rule wins for field effects. For flow actions, the first matching rule wins. Reorder them. See Conditional logic.

A condition compares against a value that is not one of the options. Health flags this as a warning. The rule will never fire. Usually the field's options were edited after the rule was written.

Last updated: 2026-09-10