Rate limits and constraints
To ensure fair use and platform stability, Rocketlane enforces rate limits and operational constraints across various app features. Familiarizing yourself with these limits helps you design efficient, reliable apps without hitting runtime errors.
Feature | Scope | Limit |
---|---|---|
Scheduler | Payload size | Maximum: 4 KB |
Job interval | Minimum: 30 minutes | |
Schedules per app | Maximum: 1 |
Note:
Jobs scheduled with intervals shorter than 30 minutes will be rejected.
Payloads exceeding 4 KB will result in a runtime error or failure to trigger.
Only one active scheduled job is allowed per app instance.
General Best Practices
- Use
r.kv
to persist additional state if your scheduler payload needs to stay lightweight. - Combine logic into a single scheduled job where possible.
- If your app requires more frequent jobs or larger payloads, contact Rocketlane support to explore whitelisting or future enhancements.
Updated about 1 month ago