Troubleshooting StretchPages

Overview

This guide collects the most common StretchPages issues and the fastest way to resolve each one, grouped by area. Work top to bottom within a section — the earlier steps resolve the majority of cases.

Access and permissions

I can't see the Pages app

1. Confirm you're signed in to the correct workspace.
2. Ask an owner or admin to verify you're an active member.
3. Ask them to confirm the Pages app is in your allowed apps — owners and admins always have access, but other members need Pages added explicitly.

A teammate can't open a page I can see

Pages are shared across everyone with Pages access. If a teammate can't open one, the cause is almost always access — have an owner/admin add the Pages app to their allowed apps.

The editor

My changes didn't stick

1. Edits autosave — there's no manual save button.
2. If you navigated away instantly after a change, reopen the page.
3. Open the Revisions panel to confirm the latest snapshot captured your work.
4. Make a small edit to trigger a fresh autosave.

The inspector is empty

Nothing is selected. Click an element on the canvas to select it, and the inspector will show its settings.

I can't place an element where I want

Elements live inside containers. Drop the element into the target container, or adjust the container's layout (flex direction, gap, grid columns) instead of trying to drag the child freely.

I made a mistake and want to go back

Use undo/redo for recent steps. For a bigger rollback, open Revisions and restore an earlier snapshot.

Responsive layout

The page looks broken on mobile

1. Switch the canvas to mobile.
2. Stack multi-column rows into a single column (select the grid/flex container and change it for that breakpoint).
3. Shrink oversized headlines.
4. Reduce horizontal padding if content overflows.

Remember: overrides only affect the breakpoint you're currently viewing.

A change I made on mobile also changed desktop

You were viewing desktop when you made it. Switch to the target breakpoint first, then make breakpoint-specific changes.

Brand and globals

A global color change didn't update an element

That element uses a local color. Select it, open the color field, and choose the global color so future changes apply automatically.

Reused sections look inconsistent

Blocks are independent copies once inserted, so edits don't propagate between them. For content that must stay identical, use a site-part instead of a block.

Popups and conditions

A popup never appears

1. Check the trigger: a delay that's too long, or a scroll point beyond the page, won't fire.
2. Check display conditions: a date range, device, or login condition may be excluding you.
3. Test on the published page — scroll and exit-intent triggers are best judged live.

An element is hidden unexpectedly

Review its display conditions. A leftover date range or device condition can hide it. Remove or adjust the condition.

Data binding

My bound section is empty

1. The chosen source may have no records. Switch to the sample source to confirm the binding works.
2. Then point it back at a source that actually has data.

Every repeated item shows the same content

Repeat is likely off, so you're seeing one record. Turn repeat on so the element renders once per record.

A field is blank on every item

That part of the element isn't mapped, or it's mapped to a field the source doesn't have. Re-check the field map against the source's fields.

Import and export

My import is incomplete or wrong

1. Read the import report to see what converted.
2. If auto-detect picked the wrong format, re-import and set the format explicitly.
3. Use the AI repair import action to fix parts that didn't convert cleanly.

A ZIP import failed

Confirm it's a valid ZIP of the expected project files, and trim very large bundles to the relevant files.

The exported code isn't a perfect match

Export produces a clean project for the chosen framework; minor structural differences are normal. Finalize the page, re-export, and integrate into your app's conventions.

Publishing and domains

I can't publish

If a custom domain is attached, verify domain ownership first — publishing is blocked until the domain's TXT record is verified. Otherwise, confirm you have edit access to the page.

My custom domain won't verify

1. Re-check the TXT record name and value against what StretchPages shows — they must match exactly, with no extra spaces.
2. DNS propagation isn't instant; wait, then click Verify again.
3. Keep the TXT record in place after it verifies.

"Domain already attached to another workspace"

A domain can belong to only one workspace. Remove it from the other StretchPages workspace, then add it here.

The site loads but there's no padlock (SSL)

SSL is issued after your DNS correctly points at StretchPages and the domain shows active. Confirm your DNS records and re-check the domain status.

My published page shows old content

Re-publish after your latest edits. Brief caching can delay updates; wait a moment and refresh.

Collaboration

I don't see a teammate's cursor

Live presence appears when you're both in the same page at the same time and connected. Confirm you're in the exact same page.

We overwrote each other's edits on one element

Split work by section using presence so two people aren't on the same element, and use Revisions to recover an earlier state if needed.

When to contact support

If an issue persists after these steps, contact StretchSuite support with:

• The page name and what you were trying to do.
• Any error message you saw.
• For domain issues, the domain name and your DNS provider.
• For import issues, the source format and, if possible, the file.

This context lets support reproduce and resolve the problem quickly.