Metaculus / Metaculus/metaculus
Investigate server action failures returning unexpected responses
Open
@cemreinanc is already working on this.
Since Feb 10, 2026.
Medium Priority
Stale
- Dominant language
- TypeScript
- Stars
- 113
- Forks
- 34
- Avg merge
- 16h 34m
- Merged PRs (30d)
- 30
Description
We're getting a lot of generic "An unexpected response was received from the server" errors from server actions.
Sentry: https://metaculus.sentry.io/issues/METACULUS-FRONTEND-20H (2,712 events, 1,491 users affected since November)
The error is thrown in Next.js's server action handler when the response isn't what's expected:
webpack://_N_E/../../src/client/components/router-reducer/reducers/server-action-reducer.ts:174:11
This is pretty generic and could be coming from multiple server actions failing. We need to add better logging to identify:
- Which server actions are failing
- What responses they're actually returning
- Whether it's a specific pattern or widespread
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.