Core
Development diagnostics and sandbox retention
Understand preparation failures and the seven-day development data policy.
Development diagnostics
Preparation failures identify invalid public reference query fields and show up to 1,000 catalog issues with omitted counts. Bounded PHP exception messages and expandable stacks provide recovery details. Core 0.8.139 requires PHP SDK 0.10.7; adopt the matching Manager runtime and CLI diagnostics. Source-only nexia check does not evaluate dynamic catalogs.
Development sandbox retention
Development databases and files are kept for seven days after sandbox creation or renewal. Renew before expiry to keep the data. After expiry, execution stops and the managed development database and files are permanently deleted. Source and project history remain, and external developer databases are not deleted. This also applies to already-expired sandboxes when deployed: export needed data before rollout.
Resource Reference reads
Large permission scopes no longer need to cause HTTP 413 when the matching platform runtime support is adopted and enabled. App code and public SDK calls are unchanged.
App preview and list loading
- Reconnecting a local development session refreshes existing App tabs to use its current runtime address.
- App GET responses up to 25 MiB can reach the browser without being rejected by the smaller mutation response limit. Writes retain their 2 MiB JSON limit. Apply the corresponding runtime update; Apps should still paginate nested collections.
- Development stylesheets can be checked against host CSS registrations across the Vite origin. Equivalent typed zero lengths (
0and0px) no longer block App styles; conflicting registrations remain rejected. - App approval settings display the owning App's translated operation names. No App source change or database migration is required.