Orphaned Job (No Runs in 30 Days)
A job definition that has not run in a month is configuration that is maintained, permissioned and inherited by whoever owns the workspace, with no output to show for it.
Free to start. No card. The playground just needs your work email.
AWSAzureGoogle CloudDatabricks
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, Azure and Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete the job that has stopped running. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Databricks Job on AWS, Databricks Job on Azure, Databricks Job on Google Cloud
- The fix, by hand on AWS
- Confirm the job is no longer needed (check its schedule and recent run history).
- Delete the job, or pause/disable its schedule if it may be needed later.
- Clean up notebooks, libraries, or clusters the job kept pinned.
These are the steps the finding carries in the product.
- Category
- Orphaned resources. Resources no longer attached to anything that needs them, such as unattached volumes and unassigned IPs.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule IDs
RC-2230RC-2330RC-2430- Full reference
Related checks
See the orphaned resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.