docs
EnglishChatigram website ↗Open Chatigram
Chatigram Pages

Pages help and troubleshooting

Resolve common Page Studio saving, workflow connection, data display, publication, access, and embedding problems.

Find the right check #

What you see What to check first
Pages or a control is unavailable Selected organization, administrator permissions, plan, and feature availability.
Save failed or a revision conflict Keep the editor open, preserve local work, and follow the recovery guidance below.
Visitors see an older design Save and explicitly publish; Auto Save changes only the draft.
Collection is empty Table, visible field mapping, current records, filter, and published revision.
Preview does not send a request Private preview suppresses workflow execution.
Workflow accepted but no result appeared Review Workflow Activity and downstream actions separately.
Publication is blocked Check for issues, publication allowance, connected resources, and FileUpload widgets.
Embedded Page does not open Public visibility and the exact allowed HTTPS origin.
Private link is unavailable Publication status, signed-in account, organization, and administrator role.

Preserve edits when saving fails #

Do not close or refresh the editor while it contains unsaved changes. Check connectivity and retry Save draft. If another edit changed the revision, preserve your local work with Advanced → Export JSON before choosing to discard and reload. Avoid overwriting a teammate’s changes without review.

Use Draft history to recover saved work. Restoring a draft does not change the live Page until you publish it. Publication history controls which earlier published version visitors see.

Understand preview and publication #

Private preview displays the saved draft and suppresses external actions and Line launches. Save before previewing. A successful visual preview does not prove that a workflow received a request or that a Line can launch publicly.

Visitors see the selected published revision. Choose Publish saved draft after changing layout, mappings, or actions. Current values in an already published data binding can update without republishing the layout, according to its update mode.

Repair an empty or stale collection #

Confirm the database and table still exist in the same organization and contain the expected records. Review Data → Database content, visible fields, and display roles. Check the selected filter and any declared URL input. Invalid or missing filter inputs can return no rows.

Review Update mode and connectivity. Tracking and filtered collections do not use general collection change notifications. Manual or periodic refresh may be appropriate. Browser backgrounding and connection interruptions can delay updates. A missing or expired feed entry may correctly show an empty state.

Check a form connection #

Use View workflow connection to confirm the event, destination, availability, and selected field names. The destination must be an enabled webhook workflow in the same organization. Attach a submission action to the enclosing Form when you need its input values.

Save and publish the corrected connection. Use a controlled synthetic submission on the published Page, then inspect Workflow Activity. Receipt of a request and completion of downstream processing are separate outcomes.

If a response was lost, check for the existing request before resubmitting. Refresh does not preserve pending operation identifiers or form values. Keep duplicate handling in workflows that perform consequential actions.

Resolve a publication problem #

Run Check for issues and follow the suggestions. Confirm your organization’s published-Page allowance and any required database, workflow, or Line availability. Public and private publications both consume slots; editing a draft does not consume another publication slot for that Page.

Remove FileUpload before publication; public guest uploads are unavailable. Confirm that a public Page does not depend on a private feed. A resource or revision change may require refreshing the saved configuration before retrying.

See the shared plan comparison and publishing guide.

Resolve access and embedding problems #

Check that the Page is still published. A private Page requires an authorized administrator in the current organization and is unavailable to signed-out visitors or cross-site embeds.

For a public embed, review Websites allowed to embed this Page (one HTTPS origin per line). Match the actual scheme, hostname, and non-default port. Do not enter a path. If chat is unavailable inside an otherwise working Page, check the Line’s own allowed website configuration and any external channel destination.

Always use the URL supplied by publication settings. Avoid guessing hostnames or reusing an old private link after access changes.

When a tracking reference returns no result #

Use the full reference and confirm the mapping points to distinct reference and status fields. Check for missing, duplicate, or expired references in the authorized source data. An unknown reference should not expose a list of other records.

Do not solve a tracking problem by making confidential fields public. Tracking references and UI conditions are not customer authentication. See public-safe tracking.

Ask for help with useful context #

Record the Page title, draft or published revision, the affected widget, exact visible error, and the time it occurred. Explain whether the problem happens in Studio, Private preview, the published link, or an embed. For workflow problems, include the relevant Activity outcome with personal information removed.

Do not share credentials, private record values, form answers, or confidential Page exports in a support report. See the general troubleshooting guide for workflow and connection checks.

Keep building.Need help with this? Explore troubleshooting ↗

Find an answer. Try “welcome workflow”, “database”, or “Telegram”.