openclaw - ✅(Solved) Fix [Bug]: Slack plugin uses deprecated files.upload API, fails with method_deprecated when sending images/files [1 pull requests, 2 comments, 2 participants]

Q: Expected behavior

Files and images should be successfully uploaded to Slack.

kinpoe-ray · 2026-03-13T02:19:35Z

[openclaw] The Slack channel plugin attempts to upload files/images using the legacy files.upload API, which Slack deprecated and has since disabled. This caus… The Slack channel plugin attempts to upload files/images using the legacy `files.upload` API, which Slack deprecated and has since disabled. This causes all file/image uploads to fail with `method_deprecated`. # PR #2: OpenClaw 紧急未修复 - Repository: haoruilee/openclaw - Author: haoruilee - State: closed | merged: False - Link: https://github.com/haoruilee/openclaw/pull/2 ## Description (problem / solution / changelog) ## Summary Describe the problem and fix in 2–5 bullets: - Problem: The Gateway crashes with an unhandled promise rejection when the Discord API returns a 503 error, as `response.json()` is called without checking `response.ok`. - Why it matters: This causes the entire gateway process to exit, leading to a complete service interruption for all connected Discord channels for several minutes. - What changed: Added a check for `response.ok` before attempting to parse the JSON response. Errors are now emitted via `this.emitter.emit("error")` and `this.handleReconnectionAttempt()` is called to trigger a graceful reconnection attempt, preventing a full process crash. Updated tests to cover the 503 error path. - What did NOT change (scope boundary): Other identified issues (#44544, #44611, #44562, #44549) were either already fixed, determined not to be code bugs, or required a dedicated test environment for safe implementation and are not part of this PR. ## Change Type (select all) - [x] Bug fix - [ ] Feature - [ ] Refactor - [ ] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [x] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [ ] Memory / storage - [x] Integrations - [ ] API / contracts - [ ] UI / DX - [ ] CI/CD / infra ## Linked Issue/PR - Closes #44529 - Related # ## User-visible / Behavior Changes The gateway will no longer crash when the Discord API returns a 503 error during client registration. Instead, it will log the error and attempt to reconnect gracefully. ## Security Impact (required) - New permissions/capabilities? (`No`) - Secrets/tokens handling changed? (`No`) - New/changed network calls? (`No`) - Command/tool execution surface changed? (`No`) - Data access scope changed? (`No`) - If any `Yes`, explain risk + mitigation: ## Repro + Verification ### Environment - OS: Linux (typical Node.js environment) - Runtime/container: Node.js - Model/provider: N/A - Integration/channel (if any): Discord - Relevant config (redacted): N/A ### Steps 1. Configure OpenClaw Gateway with a Discord integration. 2. During the `GatewayPlugin.registerClient()` call (e.g., when the health monitor triggers a Discord bot reconnection), simulate a Discord API returning a 503 HTTP status code with a non-JSON body. 3. Observe the gateway process. ### Expected - The gateway logs an error about the Discord 503 response. - The gateway attempts to reconnect to Discord without crashing the entire Node.js process. ### Actual - The gateway process crashes with an unhandled promise rejection. ## Evidence - [x] Failing test/log before + passing after (New test `should handle 503 response gracefully without crashing` added to `provider.proxy.test.ts` which now passes.) - [ ] Trace/log snippets - [ ] Screenshot/recording - [ ] Perf numbers (if relevant) ## Human Verification (required) What you personally verified (not just CI), and how: - Verified scenarios: Added and passed a new unit test specifically for the 503 error case in `provider.proxy.test.ts`, ensuring the `response.ok` check and error handling logic are correctly implemented. - Edge cases checked: Specifically addressed the case where `response.json()` would throw an error on a non-2xx response. - What you did **not** verify: Did not verify in a live production environment with an actual Discord 503 error. ## Compatibility / Migration - Backward compatible? (`Yes`) - Config/env changes? (`No`) - Migration needed? (`No`) - If yes, exact upgrade steps: ## Failure Recovery (if this breaks) - How to disable/revert this change quickly: Revert this PR. - Files/config to restore: N/A - Known bad symptoms reviewers should watch for: Gateway still crashing on Discord 503, or Discord reconnection issues. ## Risks and Mitigations - Risk: The error handling or reconnection logic might not fully cover all edge cases of Discord API errors. - Mitigation: The current fix addresses the immediate crash by preventing `response.json()` on bad responses and uses existing reconnection mechanisms. Further monitoring of Discord integration health is always recommended. <source media="(prefers-color-scheme: light)" srcset="https://cur

openclaw2026-03-13 02:19:35

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#44544•Fetched 2026-04-08 00:45:26

View on GitHub

Comments

Participants

Timeline

Reactions

Author

kinpoe-ray

Participants

0xsline

kinpoe-ray

Timeline (top)

commented ×2cross-referenced ×2labeled ×2

The Slack channel plugin attempts to upload files/images using the legacy files.upload API, which Slack deprecated and has since disabled. This causes all file/image uploads to fail with method_deprecated.

Error Message

slack tool reply failed: Error: An API error occurred: method_deprecated

Root Cause

Upload fails because the plugin calls the deprecated files.upload endpoint.

Code Example

slack tool reply failed: Error: An API error occurred: method_deprecated

---

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Steps to reproduce

Configure the Slack channel plugin with a valid bot token that has files:write scope
Ask the agent to send an image or file to a Slack channel
The upload fails

Expected behavior

Files and images should be successfully uploaded to Slack.

Actual behavior

Upload fails because the plugin calls the deprecated files.upload endpoint.

Error in logs:

slack tool reply failed: Error: An API error occurred: method_deprecated

Root Cause: Slack deprecated the files.upload API in 2024. The new API flow requires:

files.getUploadURLExternal — get a pre-signed upload URL
Upload file content directly to that URL
files.completeUploadExternal — finalize and share the file

Verified: bot token has files:write scope and files.getUploadURLExternal returns ok: true.

OpenClaw version

OpenClaw 2026.3.11 (29dc654)

Operating system

N/A (Slack API issue, not OS-specific)

Install method

No response

Model

N/A (Slack channel plugin issue)

Provider / routing chain

N/A (Slack channel plugin issue)

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

References

Slack deprecation announcement: https://api.slack.com/changelog/2024-04-a-better-way-to-upload-files
New API documentation: https://api.slack.com/methods/files.getUploadURLExternal

extent analysis

Fix Plan

To fix the issue, we need to update the Slack channel plugin to use the new files.getUploadURLExternal and files.completeUploadExternal APIs.

Step-by-Step Solution

Update the upload API endpoint:
- Replace the files.upload endpoint with files.getUploadURLExternal to get a pre-signed upload URL.
- Use the files.completeUploadExternal endpoint to finalize and share the file after uploading.
Modify the upload logic:
- First, call files.getUploadURLExternal to get the upload URL.
- Then, upload the file content directly to the obtained URL.
- Finally, call files.completeUploadExternal to complete the upload process.

Example Code Snippet

import requests

# Assuming 'token' is your bot token and 'file' is the file to be uploaded
def upload_file_to_slack(token, file):
    # Get the upload URL
    response = requests.post(
        'https://slack.com/api/files.getUploadURLExternal',
        headers={'Authorization': f'Bearer {token}'},
        json={'filename': file.filename, 'content': file.read()}
    )
    upload_url = response.json()['url']

    # Upload the file content directly to the URL
    response = requests.put(upload_url, data=file.read())
    if response.status_code != 200:
        raise Exception('Failed to upload file')

    # Complete the upload
    response = requests.post(
        'https://slack.com/api/files.completeUploadExternal',
        headers={'Authorization': f'Bearer {token}'},
        json={'url': upload_url}
    )
    if not response.json()['ok']:
        raise Exception('Failed to complete upload')

# Usage
token = 'your_bot_token'
file = open('path_to_your_file', 'rb')
upload_file_to_slack(token, file)

Verification

To verify that the fix worked, try uploading a file using the updated plugin. The file should be successfully uploaded to Slack, and you should see no method_deprecated errors in the logs.

Extra Tips

Make sure your bot token has the files:write scope.
Always check the response from the Slack API to handle any potential errors.
Refer to the Slack API documentation for the most up-to-date information on the new API flow.

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?

FAQ

Expected behavior

Files and images should be successfully uploaded to Slack.

#api #ssr #installation #tensor shape #autograd error #request error #file not found #serialization error #model compatibility

Still need to ship something?

×6

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

openclaw - ✅(Solved) Fix [Bug]: Slack plugin uses deprecated files.upload API, fails with method_deprecated when sending images/files [1 pull requests, 2 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fixed

PR fix notes

PR #2: OpenClaw 紧急未修复

Description (problem / solution / changelog)

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

User-visible / Behavior Changes

Security Impact (required)

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification (required)

Compatibility / Migration

Failure Recovery (if this breaks)

Risks and Mitigations

Changed files

Code Example

Bug type

Summary

Steps to reproduce

Expected behavior

Actual behavior

OpenClaw version

Operating system

Install method

Model

Provider / routing chain

Config file / key location

Additional provider/model setup details

Logs, screenshots, and evidence

Impact and severity

Additional information

References

extent analysis

Fix Plan

Step-by-Step Solution

Example Code Snippet

Verification

Extra Tips

FAQ

Expected behavior

Still need to ship something?

RELATED_DISCOVERY

TRENDING