Debug usability in Automation Run History

Currently, the automation run will provide a list of the completed tasks. However, the task names are generic and do not correspond with what each actions were named. This makes it very difficult to follow through the steps in complex automations to identify which ‘Create/update table record’ step failed. See a test example below:

This will become impossible if you have symmetrical actions on both side of a decision as the completed tasks will look the same.

I saw some community posts from last year calling for similar functionalities to be added. Would anyone be able to provide a roadmap on when a more robust troubleshooting experience will be available?