openclaw - 💡(How to fix) Fix [Bug]: v2026.4.27 regression — channels.discord.accounts.*.token: unresolved SecretRef "env:default:..." during openclaw gateway restart [3 comments, 3 participants]

🦞 OpenClaw 2026.4.27 (cbc2ba0) …

Restarted systemd service: openclaw-gateway.service [openclaw] Failed to start CLI: Error: channels.discord.accounts.*.token: unresolved SecretRef "env:default:...". Resolve this command against an active gateway runtime snapshot before reading it. at createUnresolvedSecretInputError (...) at resolveSecretInputString (...) at normalizeResolvedSecretInputString (...) at normalizeDiscordToken (...) at resolveDiscordToken (...) at resolveDiscordAccount (...) at Object.resolveAccount (...) at Object.resolveAccountForAccessors [as resolveAccount] (...) at Object.resolveAllowFrom (...) at buildAccountNotes (...) // status.scan.runtime

TL;DR

The issue can be resolved by ensuring that the SecretRef is properly resolved against an active gateway runtime snapshot before restarting the OpenClaw gateway service.

Guidance

• Verify that the environment variable referenced in the SecretRef is correctly set and available to the gateway service.
• Check the OpenClaw configuration to ensure that the Discord account is properly configured with the SecretRef.
• Investigate the changes made in version 2026.4.27, specifically the plugin/manifest or account-scanning changes in buildAccountNotes, to understand how they may be affecting SecretRef resolution.
• Consider reverting to a previous version or applying a workaround until the issue is fully resolved, as suggested in related issues #53098, #51263, #50537, #45838, and #39415.

Example

No code snippet is provided as the issue is related to configuration and version changes.

Notes

The issue appears to be related to a regression introduced in version 2026.4.27, and the exact cause may require further investigation. The provided error message and stack trace suggest a mismatch between the raw configuration and the resolved runtime snapshot.

Recommendation

Apply a workaround, such as reverting to a previous version or manually resolving the SecretRef, until the issue is fully resolved in a future version. This is recommended because the issue is a regression and the exact cause is not fully understood, making it safer to avoid using the affected version.