[Bug] Unable to add Symptoms while logging period for Cycle

[sreeramachandramurthy]

HealthLog version

v1.38.24

Deployment type

Self-hosted (Docker)

What happened?

Getting an error message Could not save. Try again. while adding Symptoms to a Cycle.

B.T.W. the Cycle successfully saves if I do not add any Symptoms.

Expected behavior

The Cycle should be saved when Symptoms are added

Steps to reproduce

1. Login into HealthLog (as a Female user)
2. Navigate to Cycle
3. Click on a Date (September 17th, 2026 for this screenshot)
4. Select Flow
5. Select Symptoms (Cramps and Back pain for this screenshot)
6. Click on Save

Relevant logs / screenshots

{
  "timestamp": "2026-09-18T15:21:23.899Z",
  "request_id": "4672b66c-7336-4cb2-b7c4-79cfbf178cf9",
  "trace_id": "3b3609b0-d1c9-493d-b612-ec943fd8a204",
  "kind": "http",
  "service": "healthlog",
  "environment": "production",
  "deploy": {
    "node_version": "v22.23.1",
    "hostname": "<redacted>"
  },
  "level": "warn",
  "http": {
    "method": "PATCH",
    "path": "/api/cycle/day-logs/cmu73vtdw004p01o7vhj4oadg",
    "route": "/api/cycle/day-logs/cmu73vtdw004p01o7vhj4oadg",
    "status": 422,
    "user_agent": "Mozilla/5.0 (X11; Linux x86_64; rv:155.0) Gecko/20100101 Firefox/155.0",
    "ip": "<redacted>"
  },
  "auth": {
    "user_id": "<redacted>",
    "user_role": "USER",
    "auth_method": "session",
    "record_context": {
      "epoch": 0,
      "scope": null
    },
    "provider_work_authority": {
      "origin": "owner",
      "recordUserId": "<redacted>",
      "actorUserId": "<redacted>",
      "grantId": null
    }
  },
  "action": {
    "name": "cycle.day-log.patch.validation-failed"
  },
  "meta": {
    "issue_count": 2
  },
  "duration_ms": 29,
  "runtime": {
    "loop_max_ms": 0.4,
    "loop_last_ms": 0
  }
}

Browser / OS (if applicable)

Mozilla Firefox 155.0.1 (64-bit) on Ubuntu 24.04

Pre-flight checks

• I confirmed this is not a duplicate of an existing issue.
• I redacted any secrets, tokens, or personal data from logs.

[MBombeck]

@sreeramachandramurthy thanks for this, and especially for the log. It named the cause outright.

You found a real bug, and a plain one. When you pick a symptom and do not tap an intensity for it, the sheet sends that symptom with an empty intensity. The server accepted an intensity of 1 to 4 or none at all, but not an explicitly empty one, so it refused the whole request. Two symptoms, two complaints, one 422, and all the sheet could tell you was "Could not save. Try again." Removing the symptoms made the save work, which is exactly the wrong hint: it points at the symptoms being unwelcome rather than at their missing intensity.

Nothing else in the system had a problem with it. A symptom without an intensity has always been a valid thing to store, and the code that writes it handles the empty case correctly. Only the check at the entrance disagreed, on both the create and the update path, and no test covered either. There is one now that fails without the fix.

The fix is on its way and ships with the next release. Until then, tapping an intensity on each symptom, the little 1 to 4 selector, gets the entry saved.

Thanks again for the clear report and the reproduction steps.

[sreeramachandramurthy]

Ah, I missed adding the intensity for Back pain. Gotcha. One suggestion though, having each symptom and intensity in a single line helps. While I selected Back pain, the toggles re-arranged and I missed selecting the intensity. De-cluttering the toggles might help.

[MBombeck]

Good news on the first part: you should not have needed the intensity at all. A symptom without one is a perfectly normal entry, the stored row has always allowed it, and only the check at the entrance disagreed. That is fixed and ships with the next release, so "select symptom, save" will just work.

Your layout point is a real one, and it is not you misreading the screen. Selecting a symptom makes its chip grow, because the 1 to 4 selector appears inline right next to the label. In a wrapping row that pushes everything after it along, so chips visibly move while you are still looking at the one you just picked. That is exactly how you lose the intensity you meant to tap.

I am taking that as its own item rather than folding it into the fix above, since it deserves a proper look at the layout instead of a quick nudge. One symptom per line with its intensity beside it, the way you describe, is the obvious candidate.

Thanks for both the report and the follow-up.