Why count Run Status not Showing

[AgusBudianto]

Hi Everyone

May I ask for monitoring jobs Databrick, why count Run Status not Showing

Thanks, You

Anto

[Louis_Frolio]

@AgusBudianto — we’re going to need a bit more context here.

Can you share a screenshot and clarify a few things:

• What you’re expecting to happen

• What you’re actually seeing

• Any error messages (if applicable)

The more specific you can be, the faster we can zero in on the issue and get you unstuck.

Looking forward to helping.

Cheers, Louis

[AgusBudianto]

Hi @Louis_Frolio 

You can see in the image of my first and most recent posts that on the right side is the total data for each item, for example:

active: 15
completed: 41,210
etc.

[Coffee77 · Accepted solution]

Take a look at this: https://docs.databricks.com/aws/en/jobs/monitor#finished-runs-count-graph I think that is the correct expected way of getting you're looking for.

[AgusBudianto]

ah Thanks you @Coffee77, It seems I selected the wrong tab, I should have selected the Jobs tab.

[SteveOstrowski]

Hi @AgusBudianto,

The run status counts (Active, Completed, Failed, etc.) that appear on the right side of the Workflows page are only visible when you are on the "Jobs" tab. If you are on a different tab such as "Job Runs" or "Delta Live Tables," those aggregate counts will not display.

To see the run status summary counts:

1. Navigate to Workflows in the left sidebar.
2. Make sure you select the "Jobs" tab at the top of the page.
3. The run status counts should appear on the right side of the page.

For more details on navigating and monitoring your Databricks jobs, see the documentation:
https://docs.databricks.com/en/workflows/jobs/monitor-job-runs.html

* This reply used an agent system I built to research and draft this response based on the wide set of documentation I have available and previous memory. I personally review the draft for any obvious issues and for monitoring system reliability and update it when I detect any drift, but there is still a small chance that something is inaccurate, especially if you are experimenting with brand new features.

If this answer resolves your question, could you mark it as "Accept as Solution"? That helps other users quickly find the correct fix.