Troubleshooting

Practical answers to common configuration and submission issues.

A new HighLevel field is not appearing

Reload the public form. The current object schema is retrieved whenever the form is opened or reloaded – a form already open in the browser does not automatically receive later schema changes.

A changed CRM value is not showing

Reload the form to retrieve the current record values.

An unrelated CRM field was changed elsewhere

Only the field(s) actually being changed on the form are checked for conflicts. An edit to a different field – made before or after this form was opened – has no effect on this submission at all.

The record changed after the form was opened

If a field being changed here was also changed in HighLevel since the form was opened, only that field is blocked, not the whole submission – it is a deliberate block, not “last save wins.” It's shown in place, highlighted, with the current HighLevel value and what was entered on the form. No reload is needed, and no other entered values are lost.

A required field will not submit

Check whether the field has been cleared. An existing value satisfies the requirement, but an empty required value prevents submission.

A required file field will not submit

Check whether an existing file has been marked for deletion without a replacement file being uploaded.

A Phone field rejects a number that looks valid

Every Phone-type field requires a leading country code (for example +61) – a number without one, such as 0412 345 678, is rejected. This applies to standard Contact/Opportunity/Business phone fields as well as custom ones: HighLevel's own write endpoint happens to accept a bare local number for the standard fields, but the form still requires the country code, since a number without it is ambiguous data regardless of what HighLevel will silently accept. Ask the recipient to include the country code.

Replace mode deleted no files

Replace mode only replaces existing files if a replacement file is actually uploaded. If no replacement is uploaded, existing files remain.

The form says it has already been submitted

The form was generated with multiple submissions disabled and has already been successfully submitted. The returned error may be FORM_ALREADY_SUBMITTED.

I need to disable an existing form link

Open the Forms dashboard, select the link on its object tab, and choose Retire. Access ends immediately, ahead of the configured expiry. A link also stops working on its own when it expires, or after its first successful submission when single-submit mode is enabled.

To restore access on a retired or expired link, select it and choose Reactivate 30 days. Both actions are recorded in the dashboard Change Log.

A recipient says their form is no longer available – how do I find their link?

Every message a recipient sees when a link cannot be used – expired, already submitted, record missing – now shows a Link ID and asks them to pass it on. Paste what they give you into the Link ID from recipient box on the Links page to find that exact link; a fragment of the ID is enough. From there, Reactivate 30 days restores the same URL if that is what is needed.

The ID is not the link itself and opens nothing, so it is safe for a recipient to read out, paste into a reply or screenshot.

The form says it's no longer available because a pipeline or stage may have changed

The link was generated with a Pipeline and/or Stage set on the action, and one of them no longer exists in HighLevel – most likely renamed or deleted since the link was generated. This is checked every time the link is opened. Generate a new form once the workflow's Pipeline/Stage selection is corrected.

The sub-account installed this app before Pipeline/Stage targeting was added and needs to reinstall to pick up the additional permission the dropdowns need.