Fix Supabase and integration connection issues

The app is stuck in Demo Mode

The orange ⚠️ Demo Mode (LocalStorage) indicator appears when the tool cannot detect valid Supabase credentials. Check the following:

Confirm that both VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY are set in your .env file or your hosting platform’s environment variables panel.
Make sure neither value is the placeholder text from .env.example (such as https://your-project.supabase.co or your-anon-key-here).
Restart the app or trigger a new deployment after making changes — environment variables are read at build time, not at runtime.
After restarting, do a hard refresh in your browser to clear any cached version of the app:
- Windows / Linux: Ctrl + Shift + R
- Mac: Cmd + Shift + R

If the indicator still shows Demo Mode, open your browser’s developer console (F12) and check for any error messages on page load.

VTiger CRM results don't appear in client search

VTiger CRM results in Section 0 (the client lookup step) only appear when the integration has been configured by your administrator. The integration requires the VITE_VTIGER_URL environment variable to be set, and the VTiger credentials (username and access key) to be stored as Supabase Edge Function secrets.If you are a consultant and VTiger results are not appearing, contact your administrator and ask them to verify:

VITE_VTIGER_URL is set to your VTiger instance URL
The VTiger username and access key are configured in the server-side integration settings

If you are the administrator, confirm these are set and that the VTiger integration has been fully deployed to your Supabase project.

Jira results don't appear in client search

Jira Service Management results require server-side credentials to be configured by your administrator. These are not set through the .env file — they are stored in the server’s secure configuration.If you are a consultant, contact your administrator to enable the Jira integration.If you are the administrator, verify that the Jira domain, email, and API token are all configured in your Supabase project’s secrets, and that the Jira integration has been deployed. You can retrieve your Jira API token from id.atlassian.com/manage-profile/security/api-tokens.

Quotes aren't saving to the database

Quotes are only saved to Supabase when the app is running in Supabase Mode. Check the mode indicator in the top-right corner of the app:

Green ✅ Supabase Mode — the app is connected and quotes should save. If they are still not appearing, open the browser console (F12) and look for error messages when you submit a quote.
Orange ⚠️ Demo Mode — the app is not connected to Supabase. Follow the steps in “The app is stuck in Demo Mode” above.

If the indicator shows Supabase Mode but quotes still aren’t appearing in your dashboard, the browser console will show a message at the moment of saving — look for any error in red text.

I see 'Invalid API key' in the browser console

This error means the Supabase anon key stored in VITE_SUPABASE_ANON_KEY is incorrect. The key may have been copied with missing characters, or it may have been accidentally replaced with a different value.To fix this:

Open your Supabase dashboard and go to Project Settings → API → Project API Keys.
Copy the anon / public key in full.
Update VITE_SUPABASE_ANON_KEY in your .env file or hosting platform settings.
Restart the app or trigger a new deployment.

Setup

Troubleshooting

Fix Supabase and integration connection issues