The easy workaround is to specify unique keys in your job submission. This is a good idea anyways to take advantage of job coalescing. Having said that, this can still be fixed to automatically generate a UUID when a job is submitted with no unique ID. This is a trivial fix and will be on the todo for next release.
The easy workaround is to specify unique keys in your job submission. This is a good idea anyways to take advantage of job coalescing. Having said that, this can still be fixed to automatically generate a UUID when a job is submitted with no unique ID. This is a trivial fix and will be on the todo for next release.