| The information on this page refers to v5.0 and later, which introduced the ability to queue token-based licenses. |
Queuing token-based licenses is similar to queuing regular (exclusive) 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.
- When you queue a token-based license, only the requested token-based license is queued. All of its dependencies, including token-based dependencies, remain unaffected; however, you can queue the dependencies separately.
- When multiple alternate licenses are queued, the first available will be queued and all others will be each is queued separately. When one is checked out, all others are removed from the queue.
- Fast queuing does not apply to works the same for token-based licenses as it does for exclusive licenses.
Successful checkout of a token-based license does not remove its dependencies from the queue when dependencies are queued by a separate request (as in example 1 below), unless the checkout results in the pending queued license requests exceeding the total license count (see example 2, below.) In this case, the dependencies are removed from the license queue to prevent blocking the dependency license queue, because the current client cannot check out more licenses of the dependency feature without returning some of the token-based licenses currently in use.
...