Hello @DoctorY, I took a look at both internal and external documentation and here is what I found.
Thanks for the careful timeline, it makes this a lot easier to reason about. Straight answer: I can't give you a root cause from the outside, but I can narrow it down and point you to the right escalation path.
What it isn't
The only documented auto-stop for Apps is the Free Edition limit. Apps run up to 24 hours after being started, updated, or redeployed, then stop automatically. That's 24 hours, not 6 to 7, and it isn't documented as a Premium policy. I couldn't find any public doc describing a Premium inactivity timeout, quota, or compute lease, or any customer-facing field that exposes the internal stop reason. The message you're getting ("due to workspace or account status") reads more like an account or entitlement check than an app lifecycle rule. That's a hypothesis, though, and only control-plane logs can confirm it.
Reading the evidence you have
- The missing
stopApp makes an intentional user or API stop unlikely. It doesn't prove a platform action, though, because the public audit reference doesn't promise that internal lifecycle transitions get logged as stopApp.
- I wouldn't read much into :04 / :34 yet. Your times are back-calculated from DBU quantities. If usage is aggregated or rounded at a fixed granularity, the inferred times will snap to a grid regardless of when the stop actually happened.
- A clean restart on the same source argues against a deterministic startup defect. It doesn't fully rule out a runtime crash or a health-check failure.
Capturing the next occurrence
The big gotcha: Databricks doesn't persist logs when app compute shuts down. So set these up before the next stop:
- App telemetry (Beta) or an APM tool, so the System and App logs right before the stop survive. Telemetry writes traces, logs, and metrics to Unity Catalog tables and automatically captures system logs.
- A small scheduled job that polls
GET /api/2.0/apps/{name} every few minutes and writes compute_status.state, the status message, and the UTC timestamp to a Delta table. That gives you an observed transition time, not an estimate.
- The Insights tab. If app service health shows unavailable, it's a platform issue; if only app availability is down, look at your deployment or code. That one signal could answer half your questions.
- Every
service_name = 'apps' event in each window (not just stopApp), plus account-level events (workspace_id = 0), and the Databricks status page for the same intervals.
Stopgap
In a similar thread (linked below), AmitDECopilot and DataNexus suggested first separating a crash from a clean lifecycle stop and, if it's lifecycle, using a scheduled job that restarts the app when it's found stopped. It treats the symptom, not the cause. Still, it keeps your MCP server up without touching the app config.
Escalation
For Databricks on Google Cloud, support starts with Google Cloud Customer Care, and Google and Databricks support work jointly. A Databricks support contract also lets you open a case directly. If you have neither, email help@databricks.com and tag the community managers here. Include the UTC timestamps, workspace, app, and deployment IDs, region, audit results, and logs, but share those privately, not in this thread.
At the end of the day, your evidence is enough to justify a platform-side investigation, but not enough to name the root cause yet. Capturing one stop with real timestamps and persisted logs is the fastest way to close that gap.
References:
Regards, Louis.