# `rate_limits.window_unsupported`

A rate limit's window is one its store can't count.

Area 16, [Built-in services](/docs/built-in-services.md); not declinable; the next step is usually the agent's.

Cloudflare's rate-limiting binding counts only windows of 10 or 60 seconds, so
a limit over any other window can't be counted in it:

```jadpo
application {
    apis: {
        main: {
            prefix: /
            rate_limit: {
                requests: 5
                within: 1h
            }
        }
    }
    connections: {
        limits: {
            driver: Driver.cloudflare_rate_limits
            namespace: 1001
        }
    }
    rate_limits: {
        store: limits
    }
}
```

```text
error: `within: 1h` can't be counted in Cloudflare's rate-limiting binding
 --> app.jadpo:7:25
   |
 7 |                 within: 1h
   |                         ^^ not 10 or 60 seconds
18 |         store: limits
   |                ------ counted in the binding
  reason: Cloudflare's rate-limiting binding counts only windows of 10 or 60 seconds. A Redis connection can count any window, but until Redis's driver comes each of a Worker's instances would count it in its own memory, which is the judgement call `rate_limits.counted_in_memory`.
  next: Write `within: 1m` or `within: 10s`, with `requests:` to suit, or name a Redis connection in `rate_limits: { store: }` (agent)
  rule: rate_limits.window_unsupported
  help: https://jadpo.dev/docs/errors/rate_limits.window_unsupported

check failed: 1 error, 1 file
```