How to get rid of thread conflict when the authorization key is outdated?

Question

API

Let there be a program that parses some API in X threads, and even X programs are better, they do not interact with each other. Roughly speaking, several instances of the same parser are launched, each one simply parses its own entity. At some point, the JWT authorization token becomes obsolete and each thread gets an error. Throwing all of them to log in seems irrational, because. they will file as each will get their own key. Accordingly, they will become obsolete and will not be able to come to one single key. Can you please tell me how to solve this problem?

Answer 1

Composer to check the valid key and re-request it: i.e. it manages all concurrent/asynchronous threads using the authorization key.
If the composer allowed, then the thread(s) is executed, otherwise it waits for the command.