Queuing token-base licenses is just like queuing regular licenses, except with some additional rules:
- Each token dependency must be able to be enqueued, meaning they cannot exceed any limitation, static reservation or license total count.
- Only the requested token-based license is enqueued. All of its dependencies, including token-based dependencies, remain unaffected (but they might be enqueued separately).
- When many alternate licenses are enqueued, the first available will be used, but all will be removed from the queue.
- Successful checkout of a token-based license does not remove its dependencies from the license queue (if these dependencies are enqueued separately) with one exception. When both, token-based license and one of its dependencies are enqueued separately then if after sucessful checkout of token-based license, total license count of its dependency will be exceeded counting in its request waiting in the queue, it is removed from the queue, because it would block other clients from using remaining licenses of this dependency.