Troubleshooting and getting help
Find what you are seeing, then follow the fix. Where the product shows a message, it is quoted exactly so you can search this page for it. If your problem is not here, see Getting help at the end.
Access and the admin app
Section titled “Access and the admin app”| What you see | What to do |
|---|---|
| Sliick Forms Admin is not in the App Launcher | Assign the Sliick Forms Admin permission set to the user |
| The tabs open, but every action fails | Same fix: check the user has the right permission set, fully assigned. It is not a problem with your data |
| A reviewer cannot see the Sliick Responses console | They have Sliick Forms User, which only shows the plain Form Submissions tab. Give them Sliick Forms Operator if they need the console without the builder |
| The Form Builder will not load its settings, or a setting looks wrong | The user has an old copy of the admin permission set. The builder says what it could not read. Assign the packaged Sliick Forms Admin set instead of the copy |
See Install and permission sets.
Public forms on Experience Cloud
Section titled “Public forms on Experience Cloud”| What you see | What to do |
|---|---|
| A visitor sees Unable to load form, or an access error, instead of the form | Assign Sliick Forms Submitter to the site’s guest user |
| The form loads but has no fields | Same fix. Check the permission set went to the site’s guest user, not another user |
| A visitor sees Submission failed when they click Submit | Most often the same fix: the guest user needs Sliick Forms Submitter before a public form can accept responses. If it is assigned, email support with the form’s Form ID |
| Form not available and No active form definition was found for this page. | The form has not been published, the address uses the wrong Form ID, or the guest sharing rule is missing or wrong. See Guest access for public forms |
| Form closed and This form is not accepting responses right now. | The form is paused or has closed. See Accepting responses |
| Save & continue later shows Couldn’t save your link, but the form still opens and submits | The guest user is missing access to save partly finished answers. See Guest access for public forms |
| Answers a respondent typed but had not sent or saved are gone after an upgrade to 1.2 | A one-time effect of 1.2: on an Experience Cloud or Lightning page, unsent answers kept on a device are cleared the first time the form opens there after the upgrade. Saved links are not affected |
| A respondent says their saved link stopped working | A saved link stops working once the form is submitted. If they open it again, they see You already submitted this form. From 1.2, a saved link made from a record link instead shows This link has already been used. once the record link is used. See Record links |
| That saved-answers link has expired or is no longer valid | Saved links last 7 days. The respondent starts again |
| A closed form shows in English on a site with translations | Give the guest profile access to the form’s translations. See Guest access for public forms |
| A response shows up a few seconds after it was sent | Nothing to fix. Responses from public visitors can take a few seconds to appear |
| Fields are missing from a form that worked before an upgrade | A field is not visible to the guest profile. See Upgrading the package |
Links, publishing and Sliick Edge
Section titled “Links, publishing and Sliick Edge”| What you see | What to do |
|---|---|
| Your changes do not appear on the live form | Publish the form. Edits stay in the draft until you do |
| A change does not show on your public Sliick Edge link | Publish again, then check Edge cache refresh on the Edge tab of the Delivery panel on the Admin Dashboard |
| Your Sliick Edge address says the form does not exist | In the builder, tick Allow on your public Sliick Edge address for that form, then publish |
| A form has no share link and no QR code | Set the form’s own Share URL, or set an org-wide address in the Delivery panel |
| A Sliick Edge address is refused with Another form already uses this address. Try a different one. or This address is reserved. Try a different one. | Each address belongs to one form, and a few words are kept for Sliick Edge itself. Choose another. See Each form’s Sliick Edge address |
| There is no Sliick Edge address box in New Form | From 1.2, the box shows only when the org is connected to Sliick Edge and your permission set can edit the Sliick Edge Address field. Connect Sliick Edge, then assign the packaged Sliick Forms Admin set, or add Read and Edit on that field to your own set |
| There is no Sliick Edge address box in Form settings | The org is not connected to Sliick Edge. Connect it on the Admin Dashboard’s Delivery panel |
| The Sliick Edge address box in Form settings is greyed out | Your permission set can read the Sliick Edge Address field but not edit it. The note under the box says so. Assign the packaged Sliick Forms Admin set, or add Edit on that field to your own set |
| An old link to a form on Sliick Edge stopped working after its address changed | Links and QR codes with the old address stop working when you change it. Share the new link, or use the form’s permanent link, built from its Form ID |
See Publishing a form and Sharing a form.
Installing or upgrading
Section titled “Installing or upgrading”| What you see | What to do |
|---|---|
| Salesforce refuses an install or upgrade with a message | Follow what the message says. If that does not solve it, email support@sliick.com with the message and we will help |
| This org was upgraded from an earlier version. Run the following to finish the upgrade. | Click Finish upgrade steps on the Admin Dashboard. See Finish upgrade steps |
| An upgrade step says it needs the Sliick Forms Admin permission set | Assign the packaged Sliick Forms Admin set, not a copy made before 1.1, and make sure you have Customize Application. Or add the Column value by hand, as the message explains |
| Columns blocks can’t be saved yet | Click Finish upgrade steps on the Admin Dashboard, then save again |
Responses and records
Section titled “Responses and records”| What you see | What to do |
|---|---|
| A response is marked Suspected duplicate | It looks like a second response from the same link. Open it, then click Mark as genuine or delete it. See The responses console |
| A response is marked Failed validation | It did not pass the form’s checks but was kept. Open it, correct it if needed, then click Accept for processing |
| A user you granted Create on Form Submission is told a response was accepted, but gets no submission ID back | Give that user’s permission set access to the newer response fields. See Upgrading the package |
| This form cannot accept more uploads right now. Please try again later. | The form has used its daily upload allowance. Wait, or raise the allowance. See File uploads |
| A number answer is not accepted | The Salesforce field cannot hold it, such as a fraction in a whole-number field. Publish the form again to switch on the check next to the question |
| Several people share one link ID and some answers seem missing | Everyone got the same link ID, often because a merge field in an email was empty. Give each person a different ID, and never use an email address as the ID |
| Old uploads and log entries keep building up | Nothing is removed until you schedule the clean-up flows. See Scheduled clean-up |
| A form’s webhook never arrives | Add the webhook’s website to Remote Site Settings in Setup. Slack and Teams incoming webhook addresses do not work. See Webhooks |
| Someone submitted, but no record appeared | The response has not been processed yet. Open the responses console and process it |
| The run summary says a response could not be recorded on the submission | The person processing can update the records but not the response itself. Process as someone with Sliick Forms Admin or Sliick Forms Operator, or give the person Modify All on responses. The records already created are named in the summary, so nothing is created twice |
| Processing creates duplicates instead of updating records | Tick Use for matching on the fields that identify a record, and check those fields are filled in. See Matching |
| Processing fails with a field or permission error | Processing runs as you. Check you can edit the target object and fields |
| Processing fails for every response on one form | A required field on the target object has nothing mapped to it. Add a hidden field with a default value and map it |
| A mapping that used to work has stopped | Someone renamed or deleted the target field in Setup. Map the answer again |
| A file is not on the record | Files are added when the response is processed. Check it has been processed. If the file could not be attached, the response’s Result / Error column says so |
| Two responses for the same record were processed together and the record shows a mix of both | From 1.2 that is how it works: the later response wins where they disagree, and a field only the earlier one filled in is kept. See Matching |
An error about field names, or about Name and security settings | The form and the org disagree about person accounts. See Person accounts |
See Processing responses onto records and Mapping a starter form.
Forms, fields and publishing
Section titled “Forms, fields and publishing”| What you see | What to do |
|---|---|
| Publishing is refused with a message like 2 fields share the API name ”…” | Two fields have the same API name. Rename one |
| Publishing is refused over a record type or a record link | Answer the open choice in Settings. See Record types and The form’s object model |
| A setting is greyed out in the form’s settings | Your permission set lets you read that setting but not change it. The hint under it says which one. Ask your admin |
| A logo shows on the live form but not in the builder, or the other way round | The logo’s address is approved in only one of the two places it needs to be. See Colours, fonts and logos |
| A logo or image does not show on a form on Sliick Edge | The address does not start with https://, the website holding it needs a sign-in or blocks its images on other websites, or the address is a Salesforce file’s public link page (containing /sfc/p/) rather than its download address. See Colours, fonts and logos |
| A theme colour seems to do nothing | The colour is written in a format that is not supported, so the default is used. See Colours, fonts and logos |
| A respondent cannot attach a file | The file type is not on the accepted list, the file is over 4 MB, or the form is closed. See File uploads |
| A prefill link fills nothing in | The link is more than 7 days old, was made for a different form, or the fields are not mapped |
| A record link stopped working before 7 days | It was used for a submission, or someone made a new link for the same form and record. Only one link per form and record works at a time |
| A respondent sees This link has already been used. | A response was already submitted through that record link. Record links work once. Create a new link if they need to answer again. See Record links |
| A respondent sees This link is no longer valid. | The record link was replaced by a newer one for the same form and record, or is more than 7 days old. Send the latest link, or create a new one |
| A question is never filled in from a record | Never prefill this field is ticked on it, or it is not mapped. See Record links |
| Generate link says No forms available. | No form maps a field on this record’s object. Map one, then publish |
| A save or import is refused with … is nested … levels deep or … is inside a column | Sections and repeating groups can go at most four levels deep on a page, and a Columns block cannot go inside a column. Move the block up a level or out of the column. See Sections, columns and repeating groups |
| This form uses a layout this page can’t show yet. | The form has a nested layout and the place showing it does not support those yet. Experience Cloud on 1.1 and hosted Sliick Edge forms show them. The mobile app does not yet |
| A/B experiment numbers look wrong | Publish both versions. Visitors are split at random, so a short run will not be an even split |
| The funnel shows no numbers | Funnel numbers need a connected Sliick Edge address. See Results and funnels |
Embedding on your own site
Section titled “Embedding on your own site”| What you see | What to do |
|---|---|
| The Share tab offers no embed snippet | Snippets are only offered for forms on your Sliick Edge address that do not take a payment. Allow the form on Sliick Edge and add your website to its embed allowlist |
| The embedded form is blank | Your own website is blocking it, or the page is not on the form’s embed allowlist |
See Embedding a form on your own site.
Blueprints
Section titled “Blueprints”| What you see | What to do |
|---|---|
| Importing a blueprint removed more than you expected | The file was missing fields that still existed in the form. Before importing, export the current form and compare the two |
| Exporting and importing again does not give the same form | A field has no External ID, so the import treats it as new |
| An import is refused and nothing is imported | The file comes from a newer version of Sliick Forms, or it is damaged. Upgrade this org, or export the file again |
See Blueprints and moving forms between orgs.
Getting help
Section titled “Getting help”If something is missing or does not work as this documentation describes, tell us.
- Email support@sliick.com with bugs, rough edges, a field type you need, or a way of working the builder does not fit. The people who build the product read every message.
- Install Sliick Forms from the AppExchange.
- Sliick Forms overview for what the product does and the install link.
- Book a walkthrough if you would like a demonstration.
To help us sort out a problem quickly:
- For a bug, tell us the form’s Form ID, whether the form is public or internal, and what you expected to happen. Add the package version from Setup, Installed Packages, whether the form is accepting responses and published, and whether it worked before an upgrade.
- For a processing failure, tell us the response’s status and the error shown on it.
- For a feature request, describe the task you are trying to get done, not only the feature you have in mind.