Troubleshooting and getting help
Find the symptom, check the cause. If your problem is not here, the last section on this page tells you how to reach us.
Access and the admin app
Section titled “Access and the admin app”| Symptom | Most likely cause |
|---|---|
| The app does not appear in the App Launcher | The Sliick Forms Admin permission set is not assigned |
| Tabs load but every action fails | Same: a missing permission-set assignment, not a data problem |
| A reviewer cannot see the responses console | They hold Sliick Forms User, which grants the plain submission tab only. Sliick Forms Operator is the set that grants the console without the builder |
| The Form Builder will not load its settings, or a setting reads wrongly | An admin permission set that predates a packaged field. The builder names the columns it could not read, and the remedy |
See Install and permission sets.
Public forms on Experience Cloud
Section titled “Public forms on Experience Cloud”| Symptom | Most likely cause |
|---|---|
| A visitor gets an access error instead of the form | Sliick Forms Submitter is not assigned to the site’s guest user |
| A visitor sees “Unable to load form” on an Experience page | Same cause, on the natively placed component |
| The form loads but has no fields | Same cause, or the permission set was assigned to the wrong user |
| Submitting fails with a server error | Same cause: that permission set is what lets a public form send in a submission |
| A visitor is told the form does not exist | No active form with that external ID, or the guest sharing rule is missing |
| Respondents are told a form does not exist | It was never published, or the sharing rule is missing its Was Published criterion |
| Save and continue later fails, while the form still renders and submits | The guest is missing permission to save partial answers |
| A respondent says their saved link stopped working | Reopening after submitting says the answers arrived, which is a spent link rather than an expired one. Every copy of a link is spent at submission |
| A closed form shows in English on a site with translations | The guest profile you configured lacks Read on the form’s Language and Translations fields |
| A response appears seconds after it was submitted, not immediately | Expected. Answers from an anonymous visitor are staged through a background step |
| Fields go missing from a form that worked before an upgrade | A field the runtime reads is not visible on the guest profile. See Upgrading the package |
See Guest access for public forms.
Links, publishing and Sliick Edge
Section titled “Links, publishing and Sliick Edge”| Symptom | Most likely cause |
|---|---|
| Edits do not appear on the live form | The draft has not been published |
| A change is not showing on a public Sliick Edge link | The cache refresh did not land. Publish again, and check Edge cache refresh in the Delivery panel |
| A Sliick Edge address answers “no such form” | Allow on your public Sliick Edge address is not ticked on that form |
| A form shows no share link and no QR code | No Share URL on the form and no org-wide base URL on the dashboard |
See Publishing a form and Sharing a form.
Installing or upgrading
Section titled “Installing or upgrading”| Symptom | What to do |
|---|---|
| An install or upgrade is refused with a message from Salesforce | Follow what the message says. If it does not resolve, write to support@sliick.com with the message and we will help |
Responses and records
Section titled “Responses and records”| Symptom | Most likely cause |
|---|---|
| A response is marked Suspected duplicate | It arrived under a link id another response already used, with different answers. Open the row, then Mark as genuine or delete it. See The responses console |
| A response is marked Failed validation | Its sender asked to keep responses that fail the form’s checks. Open the row, correct it if needed, then Accept for processing |
| An integration is told a response was accepted but gets no submission id | Its permission set needs Read on the new response fields. See Upgrading the package |
| Uploads are turned away for the day | The form has used its daily upload allowance. See File uploads |
| A number answer is not accepted | The Salesforce field cannot hold it, such as a fraction for a whole-number field. Republish forms that map number questions to turn on the check beside the question |
| Two respondents share one link id and some answers seem missing | The emailed id was the same for everyone, often an unfilled merge tag. Use a different id for each recipient, never an email address |
| Old uploads and log entries keep building up | Nothing is removed until you schedule the flows. See Scheduled clean-up |
| A form’s webhook never arrives | Its host is not in Salesforce’s Remote Site Settings, or the URL is a Slack or Teams incoming webhook, which turns the body away. See Webhooks |
| A respondent submits but no record appears | The submission staged and has not been processed yet. Open the responses console |
| Two responses from one respondent, seconds apart | A submit whose reply was lost, then retried. Fixed: a retried submit now produces one response, not two. Older duplicates can be deleted in the console |
| A respondent says they submitted, and nothing arrived | They pressed Submit another response on a version before this fix, and the second response was discarded as a duplicate of the first. It now starts genuinely fresh |
| The run summary says a response could not be recorded | The person processing can write the target records but not the response itself. Grant Modify All on responses, or process as an Admin or Operator. The records it did create are named, so nothing is processed twice |
| Processing creates duplicates instead of updating | The match key is incomplete on those submissions, or no field is ticked for matching |
| Processing fails with a field or permission error | Processing runs as you. Check your access to the target object and fields |
| Processing fails on every submission of one form | A required field on the target object has nothing mapped to it. Add a hidden field with a default value |
| A mapping that worked has stopped working | The target field was renamed or deleted in Setup |
| A file is not on the record | Files link at processing, not at upload. Check the response has been processed |
An error about bad field names, or about Name and security settings | A person-account mismatch. See Person accounts |
See Processing responses onto records and Mapping a starter form.
Forms, fields and publishing
Section titled “Forms, fields and publishing”| Symptom | Most likely cause |
|---|---|
| Publishing is refused, naming a duplicated name | Two fields share an API name. Rename one |
| Publishing is refused over a record type or a record link | An unanswered choice in Settings. See Record types and The form’s object model |
| A setting in Form settings is greyed out | Your permission set has read but not edit access to the field behind it. The hint under the control names it |
| A logo shows on the live form but not in the builder, or the reverse | The logo’s host is registered in one of the two places that need it. See Colours, fonts and logos |
| A theme colour appears to have no effect | The value is not in a format themes accept, so it is ignored and the default is used |
| A respondent cannot attach a file | The file type is outside 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 over 7 days old, was made for another form, or the fields are unmapped |
| A record link stopped working sooner than 7 days | It was spent by a submission, or somebody generated a new one for that form and record. There is one live link per pair |
| 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 |
| The Generate link button says “No forms available” | No form maps a field on that record’s object |
| A/B experiment numbers look wrong | Both versions must be published, and traffic is split per request, so short runs land off the nominal ratio |
| The funnel has no numbers | View and start tracking needs a connected Sliick Edge address. See Results and funnels |
Embedding on your own site
Section titled “Embedding on your own site”| Symptom | Most likely cause |
|---|---|
| The Share tab offers no embed snippet | The form collects a payment, is not on your Sliick Edge address, or has an empty embed allowlist |
| The embedded frame is blank | Your own site’s Content Security Policy, or the embedding page’s address is not on the embed allowlist |
See Embedding a form on your own site.
Blueprints
Section titled “Blueprints”| Symptom | Most likely cause |
|---|---|
| A blueprint import deletes more than expected | The incoming file omits elements that still exist. Export and compare external IDs first |
| Export and re-import do not round-trip | An element has no stable external ID, so import treats it as new |
| An import is refused outright | The file declares a newer format than this org understands, or its structure could not render. Nothing partial is written |
See Blueprints and moving forms between orgs.
Getting help
Section titled “Getting help”Everything in this documentation works today in production orgs. What is still open is the scope of 1.0: which remaining gaps matter most, and which capabilities orgs running intake need next. Your feedback decides that.
- Install Sliick Forms free from the AppExchange.
- Email support@sliick.com with bugs, rough edges, a field type you need, or a workflow the builder does not fit. Every message is read by the people who build the product.
- Sliick Forms product page for the overview and install link.
- Book a walkthrough if you would prefer a demonstration.
To help us act on a report quickly:
- For a bug, include the form’s external ID, whether the form is public or internal, and what you expected to happen. Add the installed package version from Setup, Installed Packages, whether the form is active and published, and whether it worked before an upgrade.
- For a processing failure, include the response’s status and the error shown on the row.
- For a feature request, describe the task you are trying to complete, not only the feature you have in mind.