openmcp-project / openmcp-project/backlog
Task: Deterministic Server Error handling
Open
Nobody has claimed this yet.
area/webapp
kind/task
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description
We currently remove Errors from the UI (see comment in this PR).
We are fully aware this can have implications on the End-user as they might rely on those.
Tasks:
- Identify where messages are potential skipped
- Meet with MCP engineers to foresee possible messages/states
Out of scope:
Reevaluate how we deal with server errors, e.g. with Managed Resources, when a resource kind (e.g. subaccount) had an error, we remove it silently from the UI
Contributor guide
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.
Research direction
Start by reviewing the linked pull request and tracing where server-error messages or states are removed from the UI. Consult MCP engineers about expected messages and states, then document the agreed behavior and verify that managed-resource errors are no longer silently omitted.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100