Webtask container and webtask token rate limits
A webtask token may specify rate limits that are applied when making webtask requests to execute code. Rate limits can be configured at the webtask container level or at the webtask token level. Separate rate limits can be provided for several time windows: per second, minute, hour, day, week, or month.
Webtask container rate limits
Webtask container rate limits are specified using the
ls, lm, lh, ld, lw, lo claims in the webtask token. For example, a token with a per minute limit of 100 and per day limit of 500 can execute code in a given webtask container up to 500 times in any 24h time window, but no more than 100 times in any 1 minute time window.
Webtask container rate limits are inherited in the process of token issuance. The issued webtask token will always have the same webtask container rate limits as the webtask token that autheticated the issuance. This means all webtask tokens in the issuance chain will count against the webtask container rate limit when used to execute code.
Webtask token rate limits
Webtask token rate limits are specified using the
lts, ltm, lth, ltd, ltw, lto claims in the webtask token. For example, a token with a per second limit of 5 and per hour limit of 100 can execute code up to 100 times in any 1h time window, but no more than 5 times in any 1 second time window.
Webtask token rate limits are not inherited in the process of token issuance. Usage of every token with webtask token rate limits set is accounted for separately. This mechanism allows an owner of a webtask token to decide how to subdivide its container or token rate limits across several issued webtask tokens.
Note that a webtask token can specify both per container and per token rate limits. In that case every usage of that token will count towards both classes of rate limits.