Hi Thomaz,

Thank you so much for your detailed analysis! I followed your advice and tried the following:

**What I did:**
1. Created a fresh app with a new name (`mail-agent-test`)
2. Successfully started the compute (confirmed ACTIVE state)
3. Deployed the app (deployment status: SUCCEEDED)
4. Confirmed app status: RUNNING

**Current status:**
✅ Compute Status: ACTIVE
✅ App Status: RUNNING
✅ Deployment: SUCCEEDED
❌ Browser access: Still shows "App Not Available"

**Additional findings:**
When I test the app URL with Python requests, I can see that:
- The initial request returns HTTP 302 (redirect to OAuth)
- After following redirects, it lands on the Databricks login page
- The OAuth authentication flow doesn't complete successfully
- Final URL: `https://dbc-629cd32b-8c5e.cloud.databricks.com/login.html?login_redirect_mode=none&next_url=...`

**Key discovery:**
My workspace is on **Databricks Free Edition**. According to the documentation:
- Apps auto-stop after 24 hours (as you mentioned)
- Limited to 3 apps per account
- Subject to fair usage policy

**My question:**
Could there be an OAuth/authentication limitation specific to Free Edition that prevents browser access to apps, even when the app compute is running? The fact that the OAuth flow redirects to login (rather than completing authentication) suggests a permission or tier-related restriction rather than just a compute availability issue.

The locationId errors and 403s you mentioned as "console noise" are still appearing, but as you predicted, they seem to be symptoms rather than the root cause.

Has anyone else reported similar OAuth authentication issues with Databricks Apps on Free Edition?

Thanks again for your help!