openclaw - 💡(How to fix) Fix [Discord] v2026.4.29 regression: OAuth @me fetch-timeout + native slash command deploy PATCH hits 429 during startup [1 comments, 2 participants]

• 2026-05-01T00:19:39.817Z WARN fetch-timeout (timeoutMs=2500, elapsedMs≈9524) url=https://discord.com/api/v10/oauth2/applications/@me
• 2026-05-01T00:20:42.840Z WARN fetch-timeout (timeoutMs=10000, elapsedMs≈12478) url=https://discord.com/api/v10/oauth2/applications/@me
• 2026-05-01T00:21:05.197Z WARN fetch-timeout (timeoutMs=10000, elapsedMs≈22353) url=https://discord.com/api/v10/users/@me
• 2026-05-01T00:19:45.927Z ERROR native-slash-command-deploy-rest:patch ... status=429 (You are being rate limited, retry_after ~2.637s)
• 2026-05-01T00:19:48.214Z ERROR ... status=429 (retry_after ~1.527s)
• 2026-05-01T00:19:49.208Z ERROR ... status=429 (retry_after ~3.348s)
• 2026-05-01T00:20:42.845Z ERROR ... status=429 (retry_after ~2.416s)

TL;DR

Reverting to OpenClaw v2026.4.26 resolves the Discord integration reliability issues, including fetch timeouts and rate limiting errors.

Guidance

• Verify that the issue is specific to OpenClaw v2026.4.29 by testing other versions to confirm the problem is isolated to this release.
• Review the Discord API documentation to ensure compliance with rate limiting and timeout guidelines.
• Consider implementing exponential backoff or retry mechanisms to handle temporary rate limiting errors.
• Investigate potential changes in OpenClaw v2026.4.29 that may be causing the increased traffic to Discord APIs, leading to rate limiting.

Example

No specific code example is provided, as the issue appears to be related to the OpenClaw version and its interaction with the Discord API.

Notes

The root cause of the issue is unclear, but it seems to be related to changes in OpenClaw v2026.4.29. Further investigation is needed to determine the exact cause and develop a long-term solution.

Recommendation

Apply workaround: Revert to OpenClaw v2026.4.26, as it has been confirmed to resolve the Discord integration issues. This is a temporary solution until the root cause can be identified and addressed in a future OpenClaw release.