The token is currently computed when creating the Client and there is no way to refresh it => it can exceed the maxAge parameter configured on the server.
Computing the token when executing the request should fix the issue (as it's done in Automation client)