sibljon

  // Available variables:
  // - Machine
  // - interpret
  // - assign
  // - send
  // - sendParent
  // - spawn
  // - raise
  // - actions

sibljon

// Available variables:
// - Machine
// - interpret
// - assign
// - send
// - sendParent
// - spawn
// - raise
// - actions
// - XState (all XState exports)

sibljon

// Available variables:
// - Machine
// - interpret
// - assign
// - send
// - sendParent
// - spawn
// - raise
// - actions
// - XState (all XState exports)

sibljon

{
  "page": {
    "id": "qvq7h8gxchl0",
    "name": "Spruce Health",
    "url": "https://status.sprucehealth.com",
    "time_zone": "America/Los_Angeles",
    "updated_at": "2025-11-10T23:41:11.268-08:00"
  },
  "components": [
    {

sibljon

Internal Documentation Writing Agent for Spruce Health

You are an internal documentation writer for Spruce Health. Your job is to produce comprehensive internal product documentation for any Spruce feature. The documentation targets internal teams — support, TSE (Technical Solutions Engineering), sales, engineering, and product — and must be thorough enough that any team member can understand how the feature works, who it's for, how to configure it, and how to troubleshoot it.

---

About Spruce Health

Spruce Health is a healthcare communication platform used by medical practices. Key concepts you must understand:

sibljon

Fix: Handle InvalidArgument in PostMessage resolver for message-too-long errors

Context

When a patient sends a message exceeding the 30,000-byte backend limit, the threading service returns codes.InvalidArgument. The PostMessage GraphQL resolver doesn't handle this error — it falls through as an unhandled internal error, returning data: null to the client. This causes the webapp to retry the request non-stop (1,564 times in the reported case). The fix is to catch this error and return a proper PostMessagePayload { success: false }.

Steps

1. Add MESSAGE_TOO_LONG to the GraphQL schema enum