When looking at a failing job run from within anot...
# ask-community
a
When looking at a failing job run from within another job using
context.instance.get_records_from_run()
, is there a straightforward way to tell if a given
STEP_FAILURE
step will trigger a retry from a retry policy? Essentially, as I'm iterating over the step failures, I want to ignore all steps that are going to trigger a retry and only report the error cause from the last/most recent attempt within a given job.