Currently the Play request id is implemented as an auto-incrementing long integer, which is likely to have collisions within a Play deployment consisting of multiple instances. This means it is only a suitable identifier for the request in the context of the currently running application instance.

It seems like it would make sense to have an additional request uuid and generate a random UUID for each request. This will be effectively unique across the whole system.