Skip to main content
Start with the failing visitor action and the exact error shown. Check the published public URL as well as the editor.

​
Changes appear only in preview

  1. Finish the open crop or configuration dialog.
  2. Wait for uploads and source lookups.
  3. Publish and wait for Changes published.
  4. Reload the public URL.
An editor field or dialog save can be staged without updating the live page. Page settings have their own save action. If publishing fails, correct the named field or block before retrying.

​
Missing page or content

Check the domain/alias, workspace, page availability and supported access rules. Then check the item and collection visibility. A link’s own safety, schedule or password can prevent its destination even when the Biolink loads. For custom domains, verify DNS and HTTPS using Domain troubleshooting. Test the main page load separately from sign-in and external-provider handoffs. Google Reviews is currently unavailable. A historical guide mentioning a block does not mean it exists in today’s picker.

​
Media or a provider does not load

Open the source URL directly while signed out. Check public status, region, embedding permissions and required authorization. Reconnect the correct provider account where needed. Autoplay can require muted playback or a visitor gesture. Chat participation, full music playback and protected provider content can require provider sign-in. Try the supported external interaction when embedding is unavailable. If an upload is rejected, use a supported file within its limit. For PDF, use a readable document without a password. Renaming an extension does not change the file format.

​
No response, vote or booking

Use the published page, complete required fields and wait for success. Check whether this is a native form, external signup, poll, booking or direct message: each has a different destination for results. In Contacts, confirm workspace, page, form, filters and pagination. A provider’s booking or signup is not automatically a native contact. Asynchronous metrics and exports can appear later than submission acceptance.

​
App handoff or messaging fails

Check the destination and whether a suitable email, SMS or WhatsApp app is configured. A prepared draft still needs the visitor to send it. For private messages, follow Messaging troubleshooting. Authentication, account restrictions, connection failures and microphone permissions need different remedies.

​
Get support

Provide the page URL, browser/device, approximate time, action and error. Redact private responses and messages. Never send passwords, sign-in codes, API keys or provider tokens.