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 (when dependencies are enqueued by 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 the dependency license queue, because current client cannot checkout more licenses of the dependency feature without returning some of already owned licenses.