Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"New" status not documented in the Job statuses table #122400

Open
tleverresmith opened this issue May 10, 2024 · 3 comments
Open

"New" status not documented in the Job statuses table #122400

tleverresmith opened this issue May 10, 2024 · 3 comments

Comments

@tleverresmith
Copy link

I am writing some code that checks the status of runbook jobs on an automation account. I was missing some jobs in my counts, and it looks like they are in an undocumented state.

The "New" status is used for recently submitted jobs and should be documented in the table for completeness.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@TPavanBalaji
Copy link

@tleverresmith
Thanks for your feedback! We will investigate and update as appropriate.

@AnuragSingh-MSFT
Copy link
Contributor

@tleverresmith, thank you for the feedback. Did you see the job remain in the "New" status for a prolonged period of time? Interestingly, I have never seen that status with my Runbook jobs (or I might have missed it).

@SnehaSudhirG, could you please review this feedback and share your thoughts. Thank you

@tleverresmith
Copy link
Author

@tleverresmith, thank you for the feedback. Did you see the job remain in the "New" status for a prolonged period of time? Interestingly, I have never seen that status with my Runbook jobs (or I might have missed it).

The new jobs do not stay in that status for long, 10 seconds or so at the most from what I can see. I do not see the status when looking at the portal either, only when querying using Get-AzAutomationJob.

In my scenario I am using a Runbook to read a csv from storage and start subsequent jobs from that CSV after a few checks. I put in a limiter so it cannot start too many jobs at once. That limiter checks the status of previously started jobs for their status, to see if there is any room for more, and that is where I saw the "New" status on the freshly spawned jobs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants