openclaw - 💡(How to fix) Fix [Bug]: Mattermost slash commands return 503 "not yet initialized" [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70145Fetched 2026-04-23 07:28:43
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
commented ×1cross-referenced ×1labeled ×1

This is same issue as #68113 which was prematurely closed without a merged fix.

Mattermost slash commands are not working. All commands return HTTP 503 with message "Slash commands are not yet initialized. Please try again in a moment."

Error Message

Direct requests to gateway (127.0.0.1:18788) and through nginx proxy both fail with same error

Root Cause

This is same issue as #68113 which was prematurely closed without a merged fix.

Mattermost slash commands are not working. All commands return HTTP 503 with message "Slash commands are not yet initialized. Please try again in a moment."

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

This is same issue as #68113 which was prematurely closed without a merged fix.

Mattermost slash commands are not working. All commands return HTTP 503 with message "Slash commands are not yet initialized. Please try again in a moment."

Steps to reproduce

  1. Start openclaw with mattermost enabled.
  2. Wait for '[mattermost] slash commands registered (32 commands across 1 teams, callback=http://<gateway_ip>:18789/api/channels/mattermost/command)'
  3. curl http://<gateway_ip>:18789/api/channels/mattermost/command | jq Returns. { "response_type": "ephemeral", "text": "Slash commands are not yet initialized. Please try again in a moment." }

Expected behavior

Slash command should execute successfully and return the requested information (e.g., gateway status for /oc_status).

According to OpenClaw documentation, GET request to /api/channels/mattermost/command should return 405 Method Not Allowed when the handler is properly initialized.

Actual behavior

Commands are successfully registered in Mattermost (33 commands) Gateway logs show: [mattermost] slash commands activated for account default (33 commands) But all slash commands return: {"response_type":"ephemeral","text":"Slash commands are not yet initialized. Please try again in a moment."} GET request to callback endpoint returns HTTP 503 instead of expected 405 Method Not Allowed Problem persists even 90+ seconds after gateway startup Direct requests to gateway (127.0.0.1:18788) and through nginx proxy both fail with same error

OpenClaw version

2026.4.21

Operating system

linux

Install method

docker

Model

anthropic/claude-opus-4-6

Provider / routing chain

n/a

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue with Mattermost slash commands returning an HTTP 503 error may be related to the initialization status of the slash commands, and a potential fix could involve verifying the initialization process or checking the OpenClaw configuration.

Guidance

  • Verify that the slash commands are properly initialized by checking the OpenClaw logs for any errors or warnings related to the initialization process.
  • Check the OpenClaw configuration to ensure that the Mattermost integration is correctly set up and that the callback endpoint is properly defined.
  • Investigate why the GET request to the callback endpoint returns an HTTP 503 error instead of the expected 405 Method Not Allowed, as this could indicate a misconfiguration or an issue with the handler initialization.
  • Consider testing the slash commands after a longer period than 90 seconds to see if the issue persists, as the error message suggests trying again in a moment.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue seems to be related to a previous issue (#68113) that was prematurely closed without a merged fix, which may indicate that the problem is not fully resolved. Additionally, the fact that the issue persists even after 90 seconds suggests that the problem may not be related to a simple initialization delay.

Recommendation

Apply workaround: Given the lack of information about the specific cause of the issue, it may be necessary to apply a workaround, such as manually initializing the slash commands or modifying the OpenClaw configuration to bypass the initialization check.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Slash command should execute successfully and return the requested information (e.g., gateway status for /oc_status).

According to OpenClaw documentation, GET request to /api/channels/mattermost/command should return 405 Method Not Allowed when the handler is properly initialized.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Mattermost slash commands return 503 "not yet initialized" [1 comments, 2 participants]