Queuing token-base based licenses is just like similar to queuing regular licenses, except with some the following additional rules:
- Each token dependency must be able to be enqueued, meaning they cannot exceed any queued in accordance with any set limitation, static reservation or license total count.
- Only the requested token-based license is enqueuedqueued. All of its dependencies, including token-based dependencies, remain unaffected (but however, they might may be enqueued queued separately).
- When many multiple alternate licenses are enqueuedqueued, the first available will be used, but queued and all others will be removed from the queue.
- Successful checkout of a token-based license does not remove its dependencies from the license queue (when dependencies are enqueued queued by a separate request) with one exception. Sucessful checkout of token-based license resulting in dependency total license count exceeded by license request pending in the queue results in removal of the dependency request from the queue. Leaving it there might block , 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 already owned the licenses currently in use.