Queuing token-based licenses is similar to queuing regular licenses, with the following additional rules:
- Each token dependency must be able to be queued in accordance with any set limitation, reservation or license total count.
- Only the requested token-based license is queued. All of its dependencies, including token-based dependencies, remain unaffected (however, they may be queued separately).
- When multiple alternate licenses are queued, the first available will be queued and all others will be removed from the queue.
- Successful checkout of a token-based license does not remove its dependencies from the queue (when dependencies are queued by a separate request), except when the checkout results in the pending queued license requests exceeding the total license count. In this case, removing the dependencies from the license queue prevents blocking the dependency license queue, because the current client cannot checkout more licenses of the dependency feature without returning some of the licenses currently in use.