Troubleshooting

Start from the failed action and safe status. Avoid changing permissions or financial data until you understand the owning boundary.

Build and configuration

App build cannot find Supabase configuration: configure required variables in the intended build/runtime environment. The independent docs build needs no Supabase key.

Links use the wrong host: compare canonical app/docs origins, provider Site URL and allowed redirect destinations. Rebuild when embedded public variables change.

Account access

Provider sign-in works but Helm refuses: check the actual owned session, admission mode and scopes. Do not weaken ownership checks as a setup fix.

Recovery mail does not arrive: distinguish accepted request from delivery. Review configured mail transport, the entered address and provider diagnostics safely. Do not enable confirmation-dependent flows before transport works.

Imports and financial reads

Import appears paused: inspect its existing job and worker invocation. Continue that job rather than uploading another copy. Cancel may leave already committed work visible.

Balance is unavailable: use the safe request ID/status to inspect provider or database availability. Do not turn the error into zero.

Account saved but balance failed: recover the statement on the same account. Do not repeat account creation.

Documentation search

Verify Pagefind ran after the Next build and public/_pagefind is included in the deployed output. Test an actual published route’s text, then inspect asset responses if search still fails.

Use deployment sequence and error reference for the specific recovery.