Hey @geekodour,

Thanks again for taking the time to report this, we are working on it internally and I’ll post an update here as soon as I have news.

Thanks again. Meanwhile, we’re looking forward to seeing you around!

Just to be even more clear about my question, I think job.steps.\<step_id\>.status does not exist yet. as job context is just

{
  "status": "Success"
}

and steps context is just {}

@andreagriffiths11 any update on this?  

While i understand that the product is still in beta, I think it is more useful to only release docs for api/endpoints that work; not things that we hope will work in the future.

Time is my most valuable asset and it is really frustrating to invest time using/learning a new product only to learn that particular endpoint isn’t working “YET” and no clear instructions on alternatives to use in the meantime.

Try

if: job.steps.<step id>.status == failure()

It doesn’t work either way because job.steps.<step id>.status is null. job is the following simple object:

{
    "status": "Success"
}

As you can see, it doesn’t even have a steps property, let alone anything below that.

Since I’m finding many parts of the docs are still more like a whishlist, I’m starting this repo, that tracks progress of the missing features: https://github.com/meeDamian/github-actions-bugs/actions, I’ll be adding one feature check, per scheduled daily workflow file.  Feel free to contribute, or peek-in to see if it’s already implemented :).