However, that is avoiding the real world use case. I am hopeful that there may be a better way in Gatling to handle that rather than changing my use case.
I can think of storing those activation tokens in a mutable data structure in the session object and using it later. But wondering if anyone else has any suggestion for me or thought about it.
Take a look at Gatling’s Redis Feeder (only used for reading from Redis - but you can get the idea of how the client works - it’s pretty simple to implement both read and write yourself):