The image above is from the demo job 282774173, but it also occurs on my private RiverUI on version 0.10.0.
As shown on the image, all attempt times are synced to the latest retry (in this case "less than a minute ago"), rather than when they actually occurred.
I haven't taken a look at the implementation, but it seems the attempted_at field in the response is being used for all attempts which is inaccurate.
Perhaps it would be better to parse the attempted_by items to get the actual time of the attempts.
The image above is from the demo job 282774173, but it also occurs on my private RiverUI on version 0.10.0.
As shown on the image, all attempt times are synced to the latest retry (in this case "less than a minute ago"), rather than when they actually occurred.
I haven't taken a look at the implementation, but it seems the
attempted_atfield in the response is being used for all attempts which is inaccurate.Perhaps it would be better to parse the
attempted_byitems to get the actual time of the attempts.