SQLite rate limits and usage caps block work
2 posts from 2 people2d activeSteady, +1 this weekunverified
Posts per day
The posts behind it
rivetkit 3.0 docs: a crash can keep a `c.db` row but lose the `c.state` change made just before it
### Summary `c.state` is saved on a throttle: a change made less than `stateSaveInterval` (1 s) after the previous save waits for the rest of that interval (`throttled_save_delay` in `rivetkit-core/src/actor/state.rs`). A write to `c.db` commits at once. So when the process dies...
Assistant 429s itself: "too many requests in progress for this sandbox" during knowledge-base materialization
...Assistant should respect 429s - throttle concurrency and retry with backoff - instead of failing the task. Alternatively, expose the per-sandbox in-flight limit as a tunable on the sandbox API (no env var exists for it in 1.7.0). ### Environment - n8n 2.42.7 self-hosted (Docker,...
Companies and products named
About this problem
Evidence
2 posts from 2 people in 2 places, about 1 a week over 23 days. Mostly on n8n-io/n8n, rivet-dev/rivet. Tools named alongside: Docker, n8n.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "rate-limits" rule about SQLite. First post Oct 12, 2026, latest Nov 3, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
API rate limits and usage caps block real work
40 posts from 39 people on GitHub issues, Hacker News, Reddit.
Claude Code rate limits and usage caps block work
20 posts from 20 people on GitHub issues, Reddit, Hacker News.
Claude rate limits and usage caps block work
19 posts from 19 people on Reddit, App Store reviews, GitHub issues.
Codex rate limits and usage caps block work
16 posts from 16 people on GitHub issues.
ChatGPT rate limits and usage caps block work
16 posts from 16 people on GitHub issues, Reddit, Stack Overflow.
Anthropic rate limits and usage caps block work
12 posts from 9 people on GitHub issues, Reddit, Community forums.
GitHub rate limits and usage caps block work
10 posts from 9 people on GitHub issues, Hacker News.
Model Context Protocol rate limits and usage caps block work
9 posts from 6 people on GitHub issues, Hacker News.
Gemini rate limits and usage caps block work
9 posts from 9 people on GitHub issues, Reddit, App Store reviews.
OpenAI rate limits and usage caps block work
6 posts from 6 people on GitHub issues, Community forums.
Redis rate limits and usage caps block work
6 posts from 6 people on GitHub issues.
MLflow rate limits and usage caps block work
5 posts from 5 people on GitHub issues.
Other SQLite problems
SQLite upgrades break working setups
18 posts from 17 people on GitHub issues.
SQLite users keep filing bugs
Top post: "filelock<4.0 cap keeps downstreams on a version with three open CVEs", one of 39 posts from 35 people on GitHub issues, Reddit.
Trouble with SQLite node
Top post: "The Remove Duplicates node gets stuck at maximum history size", one of 5 posts from 5 people on GitHub issues.
Trouble with SQLite mode
Top post: "HTTP Request parses top-level JSON strings twice in Autodetect response mode", one of 2 posts from 2 people on GitHub issues. Unverified.
Trouble with SQLite response
Top post: "Provide More Context When the Error Something Went Wrong Before I Could Finish That Response Occurs", one of 2 posts from 2 people on GitHub issues. Unverified.
SQLite lock-in makes switching costly
2 posts from 2 people on GitHub issues. Unverified.
History