Get unique environment variable to detect a 'retry' of job

At, we load balance end-to-end tests and part of this functionality is dependent on looking at the environment variables to tie jobs from different machines together.

When you ‘retry’ a job manually, everything goes wrong - the retried job has the exact same environment variables as the initially run job.

Is there a way to detect if a job has been retried, to uniquely identify it from the initially run job?

1 Like

Just wondering the same, so… “bump” I guess? My use case would be enable some verbose logging in a job when it’s retried.