Registration token problem for ephemeral runners?

[usernamessh]

Hello community,

maybe I got something wrong. But ARC is using ephemeral runners. So when a job is over, the runner gets deleted.
The next runner needs to be registered afterwards - it will need to have a fresh Registration Token? Or when creating new runners while doing the horizontal scaling, here as well fresh Registration Token are required?

-> How is that supposed to happen to provide fresh Registration Tokens then? I think I got something wrong. Can someone please explain? After reading the docs several times, it is not clear to me.

I am asking because I am getting runner registration errors in my AKS pods after the first successful run of a runner.

Please notice:
I am running Windows runners and using the suggested Dockerfile that can be found here in the documentation.
The Dockerfile in the docu section "Configuring Windows Runners" has this $enf:RUNNER_TOKEN variable in the entrypoint powershell call. But where is it supposed to come from automatically? With fresh Registration Token every time?

[usernamessh]

Ok, now I understood :-) The environment variables, which hold the token and the runner-name, are maintained automatically by the context. That's great! It is working just fine! My question is now solved :-)