Databricks Apps - "App Not Available" error with locationId parameter missing

[yutmurakami]

Hello,

I'm experiencing an issue with Databricks Apps where I cannot access my deployed app from a browser, even though the app appears to be running successfully.

**Symptoms:**
- Browser shows "App Not Available" error when accessing the app URL
- Console errors show:
- "BAD_REQUEST: Missing or invalid required parameter: locationId"
- "403 Forbidden on /ajax-api/2.0/apps/[app-name]"
- WebSocket connection failures

**Environment:**
- Workspace ID: 7474651874855137
- Workspace URL: https://dbc-629cd32b-8c5e.cloud.databricks.com
- App Name: mail-agent-ui-v2
- App URL: https://mail-agent-ui-v2-7474651874855137.aws.databricksapps.com
- Region: AWS

**What I've confirmed:**
✅App is successfully deployed (state: SUCCEEDED)
✅Streamlit server is running normally (verified in logs)
✅No errors in application logs
✅curl/Python requests return 302 redirect (OAuth flow starts correctly)
✅Tested from multiple browsers and networks (home Wi-Fi, mobile)
✅App compute shows: "App compute was stopped due to workspace or account status"

**Additional observation:**
The app was automatically stopped with the message "App compute was stopped due to workspace or account status", which suggests there might be a workspace or account-level restriction.

**Questions:**
1. Is there a workspace or account setting that needs to be enabled for Databricks Apps?
2. Could this be related to authentication/authorization at the workspace level?
3. Has anyone else experienced this locationId parameter error?

The app itself appears to be working correctly internally, but the OAuth authentication flow seems to fail when accessed from a browser.

Any help or suggestions would be greatly appreciated!

[ThomazNeto]

Hey — I think the answer is hiding in your own checklist, in that last item you marked with a ✓:

"App compute was stopped due to workspace or account status"

That's not a side observation, that's almost certainly your root cause. In Databricks Apps, *deployment* and *compute* are separate states. Your deployment can be SUCCEEDED (code packaged and published) while the app's compute is stopped — and a stopped app is simply not accessible from the browser. "App Not Available" is the expected page for that state, not a bug in your app. The Streamlit logs showing the server running normally are most likely from before the stop.

The 302 you get from curl doesn't contradict this either — that just means the ingress/OAuth layer in front of the app is up. It responds even when the compute behind it is down.

On the locationId error and the 403 on /ajax-api: I went looking and couldn't find any public documentation or thread on that locationId parameter. My read (opinion, not verified) is that both are console noise — internal workspace UI calls failing as a *consequence* of the app/account state, not the cause. I wouldn't spend time debugging those before sorting out the compute status.

So, to your questions:

1. It's less about a setting to enable and more about what "workspace or account status" means for your environment. What kind of workspace is this — Free Edition, trial, or paid? That changes everything:
- Free Edition: apps auto-stop after a period (24h has been cited), there's a one-app-per-account limit, and if you exceed the fair-usage quota, compute gets shut down for the rest of the day (or in extreme cases the month). All of these produce exactly the stop you're seeing, and all are recoverable — just restart later.
- Paid: Apps require Premium/Enterprise tier; they don't work on Standard by design.
- Trial: an expired trial or a billing/subscription issue at the account level would also surface as a stop "due to account status" — that one you'd check in the account console.

2. I don't think this is an auth problem. Your OAuth flow starting correctly (the 302) actually confirms that layer is fine.

3. See above — no public reference I could find, so you're probably looking at UI internals rather than something actionable.

What I'd do, in order: just try starting the app again (Start button in the Apps UI, or `databricks apps start <app-name>` from the CLI). If it was an auto-stop or a daily quota, that alone fixes it — or it fails with a clearer message, which is also progress. If Start keeps failing with the same "workspace or account status" message and your account/billing looks healthy, then it's a support ticket, and you already have everything they'll ask for (workspace ID, app URL, timestamps)