Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: The saved configuration changes for the channel did not take effect. [2 pull requests, 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#48923•Fetched 2026-04-08 00:51:00
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Author
zongyanglaobiaozongyanglaobiao
Participants
RyceRycezongyanglaobiaozongyanglaobiao
Timeline (top)
referenced ×3cross-referenced ×2labeled ×2commented ×1

current version: 2026.3.13 Just as a side note, that version is like this across the board.

Root Cause

current version: 2026.3.13 Just as a side note, that version is like this across the board.

Fix Action

Fixed

PR fix notes

PR #48937: fix(ui): display error message when channel config save fails

Description (problem / solution / changelog)

Summary

Fixes #48923 - Channel config save fails silently with no error feedback

Root Cause

The saveConfig() function sets state.lastError on failure, but the Channels UI never displayed it. Users saw unresponsive page with no feedback, making it impossible to diagnose config save failures.

Fix

  1. Check props.lastError in renderChannelConfigSection
  2. Display error in danger callout when present
  3. Error clears on next successful save

Testing

  • Error message displays when save fails
  • Error message clears on successful save
  • No breaking changes to existing functionality

Related Issue

Fixes #48923

Changed files

  • extensions/telegram/src/send.ts (modified, +14/-1)
  • ui/src/ui/views/channels.config.ts (modified, +10/-0)

PR #48952: fix(ui): display error message when channel config save fails

Description (problem / solution / changelog)

Summary

Fixes #48923 - Channel config save fails silently with no error feedback

Root Cause

The saveConfig() function sets state.lastError on failure, but the Channels UI never displayed it. Users saw unresponsive page with no feedback.

Fix

  1. Check props.lastError in renderChannelConfigSection
  2. Display error in danger callout when present
  3. Error clears on next successful save

Testing

  • Error message displays when save fails
  • Error message clears on successful save
  • No breaking changes

Related Issue

Fixes #48923

Changed files

  • ui/src/ui/app-channels.ts (modified, +6/-0)
  • ui/src/ui/views/channels.config.ts (modified, +11/-1)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

current version: 2026.3.13 Just as a side note, that version is like this across the board.

Steps to reproduce

  1. Access the Web UI page and click on "Channels".
  2. No matter what configuration I modify, clicking "Save" results in an unresponsiveness. After refreshing, none of the changes I made have taken effect.

Expected behavior

After clicking, a "Save Successful" message or some other notification should be displayed.

Actual behavior

Page Unresponsive

OpenClaw version

2026.3.13

Operating system

Ubuntu 24.04.4 LTS

Install method

npm

Model

minmax

Provider / routing chain

none

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

The fix involves modifying the save functionality to handle asynchronous operations and provide feedback to the user.

Steps to Fix

  • Modify the save button click event handler to use asynchronous programming:
    • Use async/await to wait for the save operation to complete
    • Display a "Saving..." message to the user while the operation is in progress
    • Display a "Save Successful" message when the operation completes
  • Update the save operation to return a promise that resolves when the operation is complete

Example Code

// Before
function saveChanges() {
  // Save operation code here
}

// After
async function saveChanges() {
  try {
    // Display "Saving..." message to the user
    displayMessage("Saving...");
    
    // Save operation code here
    await saveOperation();
    
    // Display "Save Successful" message to the user
    displayMessage("Save Successful");
  } catch (error) {
    // Handle any errors that occur during the save operation
    displayError("Error saving changes: " + error.message);
  }
}

function saveOperation() {
  return new Promise((resolve, reject) => {
    // Save operation code here
    // Call resolve when the operation is complete
    resolve();
  });
}

Verification

To verify that the fix worked, follow these steps:

  • Access the Web UI page and click on "Channels"
  • Make some changes to the configuration
  • Click the "Save" button
  • Verify that a "Saving..." message is displayed to the user
  • Verify that a "Save Successful" message is displayed to the user when the save operation is complete
  • Verify that the changes are saved correctly by refreshing the page and checking the configuration

Extra Tips

  • Make sure to handle any errors that occur during the save operation to prevent the page from becoming unresponsive
  • Consider adding a timeout to the save operation to prevent it from taking too long
  • Use a logging mechanism to log any errors that occur during the save operation for debugging purposes

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

After clicking, a "Save Successful" message or some other notification should be displayed.

#api#ssr#installation#tensor shape#autograd error#configuration error#environment variable#network issue#logging issue#authentication issue

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 - ✅(Solved) Fix [Bug]: The saved configuration changes for the channel did not take effect. [2 pull requests, 1 comments, 2 participants]