monday.com status writes can fail with HTTP 200; mirror and formula columns read differently
Never trust HTTP 200 alone on a status change; re-query the item and confirm the value actually moved.
monday.com status writes can fail with HTTP 200; mirror and formula columns read differently
TL;DR
Never trust HTTP 200 alone on a status change; re-query the item and confirm the value actually moved. Read formula columns from display_value, not text or value. For connect-boards and mirror columns, expect null text/value and plan a different read path.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
When a write silently fails, check the mutation's error fields in the response body, not the transport status.
Context: Community reference (skills-il monday-com-workflows domain checklist): documents the column-value quirks that trip agents reading monday.com boards. Connect-boards and mirror columns return null for text and value, so reading them like normal columns yields nothing. Formula columns return their result in display_value while text and value stay unpopulated. And status writes can fail while the API still answers HTTP 200, so the status code tells you nothing about whether the write landed.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.