Error: gateway timeout after 30000ms
✅Solved
How to increase timeout for this Error: gateway timeout after 30000ms
Solution
That pattern (job actually runs +
So: nothing to “increase” here — it’s basically a false-negative / UX bug.
What you can do:
- Ignore the CLI error and rely on:
(authoritative source of whether it ran)
- Upgrade OpenClaw as fixes land (you’re on 2026.2.26). This is the only real way it’ll stop being annoying.
- If you want to help get it fixed faster: add a quick “me too” + your environment details to the issue (same version, npm global, systemd user service, loopback) and mention that runs are OK; only
https://github.com/openclaw/openclaw/issues/29601
cron runs …okopenclaw cron rungateway timeout after 30000mscron runSo: nothing to “increase” here — it’s basically a false-negative / UX bug.
What you can do:
- Ignore the CLI error and rely on:
(authoritative source of whether it ran)
- Upgrade OpenClaw as fixes land (you’re on 2026.2.26). This is the only real way it’ll stop being annoying.
- If you want to help get it fixed faster: add a quick “me too” + your environment details to the issue (same version, npm global, systemd user service, loopback) and mention that runs are OK; only
cron runhttps://github.com/openclaw/openclaw/issues/29601
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
