I'm using the Generic REST collector to collect data from a REST API Endpoint using token authentication. I have Get Token from URL configured and it works correctly when I click Generate Authentication Token in the connection configuration. I successfully get a token this way. The returned token is placed into ${AuthenticationToken}, and called in the authentication header. I am able to successfully make REST calls and everything works.

However, it appears that scheduled collections reuse the token generated during configuration rather than requesting a new token from the configured Token URL when the collection runs on subsequent runs. Because the CyberArk token expires, scheduled collections fail with HTTP 401. Is the Generic REST collector supposed to call the configured Token URL and refresh the token at the beginning of each collection run?

If not, what is the recommended approach for an API that requires a new short-lived authentication token for each collection? OAUTH is not an option for this platform, and neither is Basic Authentication.