When Base44 publish says success but live is unchanged

A common stuck moment: the UI says publish succeeded, but the live URL still shows yesterday’s version — or a blank screen.

Treat these as different faults. A failed build needs logs. A “success” with stale live output may be caching, a wrong publish target, or a change that never left preview. A blank screen after an AI edit needs the last change and any console error you can copy.

Check platform status first, then capture the exact message. We walk triage on /base44-not-working.

We do not invent incident queues. If you want a human pass, use /start with type publish.