Yes, we want to allow for this. Might take some work to validate we can do this in azure devops. But this will allow for better visibility that the start eval makes this ID and then the wait for event is using this ID. If there are ever two parrallel events in-flight, then this can support that use case too.
Yes, we want to allow for this. Might take some work to validate we can do this in azure devops. But this will allow for better visibility that the start eval makes this ID and then the wait for event is using this ID. If there are ever two parrallel events in-flight, then this can support that use case too.