Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: wecommcp smartsheetadd_records returns success but data not persisted in sub-sheets [1 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#58936•Fetched 2026-04-08 02:30:58
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
rachelhuangrachelhuang
Participants
rachelhuangrachelhuang
Timeline (top)
labeled ×2

When using smartsheetaddrecords or smartsheetupdaterecords on a sub-sheet (child sheet of a smartsheet document), the API returns {"errcode": 0, "errmsg": "ok"} but the data is never actually persisted.

Root Cause

When using smartsheetaddrecords or smartsheetupdaterecords on a sub-sheet (child sheet of a smartsheet document), the API returns {"errcode": 0, "errmsg": "ok"} but the data is never actually persisted.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

When using smartsheetaddrecords or smartsheetupdaterecords on a sub-sheet (child sheet of a smartsheet document), the API returns {"errcode": 0, "errmsg": "ok"} but the data is never actually persisted.

Steps to reproduce

  1. Create a smartsheet document with multiple sub-sheets
  2. Call smartsheetaddrecords to add records with data to a sub-sheet
  3. API returns success with record IDs and data in response
  4. Immediately call smartsheetgetrecords - returned records exist but all cell values are empty {}
  5. Viewing the document in WeChat Work app shows records with "—" in all cells

Expected behavior

  • Expected: Data written via add/update should be persisted and retrievable

Actual behavior

  • Actual: API returns success but get_records shows empty values {}

OpenClaw version

2026.3.7

Operating system

Ubuntu 24.04 LTS (Noble Numbat)

Install method

No response

Model

MiniMax-M2.7 (via minimax-portal)

Provider / routing chain

WeChat → OpenClaw Gateway (local) → WeCom Plugin → MiniMax M2.7

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

  • This only affects sub-sheets. Main/summary sheets work correctly.
  • Main sheet record updates work fine
  • The bug is 100% reproducible on sub-sheets
  • The MCP server appears to return the written data in the response (mimicking success) but it is not actually persisted in WeCom's backend

extent analysis

TL;DR

The issue can be mitigated by verifying the data persistence in the WeCom backend after calling smartsheetaddrecords or smartsheetupdaterecords on a sub-sheet.

Guidance

  • Investigate the WeCom backend to determine why the data is not being persisted, despite the API returning a success response.
  • Verify that the issue is specific to sub-sheets and not a general problem with the smartsheetaddrecords and smartsheetupdaterecords APIs.
  • Check the OpenClaw Gateway and WeCom Plugin configurations to ensure they are correctly set up to handle sub-sheet data persistence.
  • Test the APIs with a different provider or routing chain to isolate the issue.

Example

No code snippet is provided as the issue is related to the interaction between multiple systems and APIs.

Notes

The issue seems to be related to the interaction between the OpenClaw Gateway, WeCom Plugin, and WeCom backend. Further investigation is needed to determine the root cause of the problem.

Recommendation

Apply a workaround by implementing additional error checking and data verification after calling smartsheetaddrecords or smartsheetupdaterecords on a sub-sheet, to ensure that the data is actually persisted in the WeCom backend.

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

  • Expected: Data written via add/update should be persisted and retrievable
#api#retriever error#indexing error#inference speed#output truncation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING