For a ChangeEvent that may be executed multiple times within a single pipeline, it would be nice if the timestamp posted to pagerduty was the exact time that the step executed, it will be ordered correctly, increasing it's usability.

Here is an example of 3 change events posted by the same job, that show out of order of their actual execution.