Illustrative visitor input
Visitor report
Profile save fails when the time zone is blank
Problem · Example Site · Profile settings
I selected Save on my profile, but the page showed an error and kept the old details.
Illustrative example
A report result that keeps evidence, conclusion, and unknown facts separate.
This example uses a fictional website and source snapshot. It shows the customer review structure without a claim about a real user or result.
Safe browser evidence
EV-001
Failed request metadata
POST /api/profile → 500 in 412 ms
No query values, headers, or bodies.
EV-002
Form-field metadata
time-zone · present: false · size: 0
No form value.
Source evidence
EV-003
Example source snapshot 4f7a2c1
src/routes/profile.ts:118–124
const zone = profile.timeZone.trim();
return saveProfile({ ...profile, timeZone: zone });The cited branch uses the field before an absent-value check.
Evidence assessment
Conclusion
The save path likely does not handle an absent time-zone field.
The failed request, missing field metadata, and cited source branch form a related evidence chain.
Limit: The example does not prove how many profiles have this state or whether every request used the same release.
Unknown facts
- The number of affected profiles. The approved evidence contains one report, not an aggregate count.
- The complete release distribution. The example identifies one source snapshot only.
Recommended action
Handle an absent time-zone value before the save path uses it.
- Add a null-safe branch.
- Add a focused regression test for an absent time zone.
- Use the normal human review and release process.
Low risk Human approval is required.
Draft response
Thank you for the report. We found a likely issue in the active profile save path. The website owner will review the recommended change before release.
The owner can edit and copy this draft. IssueProbe does not send it.