Describe the bug

When a launchplan is executed as part of a Flyte workflow FlytePropeller is responsible for generating an execution ID. This algorithm must be deterministic so that subsequent workflow processing checks the correct launchplan execution ID to retrieve status. Currently it uses a 32bit hash of the subworkflow node ID. However, this only produces a 8 character (actually 7 and 1 padded) execution ID. With a large number of launchplan executions collisions may occur.

Expected behavior

Launchplan executions ID should never collide.

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes