# FM-KED-008 — HTTP 500 Internal Server Error (Application Error)

**Severity:**<span style="white-space: pre-wrap;"> S2 — High</span>  
**Recovery Class:**<span style="white-space: pre-wrap;"> D — Exploratory</span>  
**Covered by Monthly Support:**<span style="white-space: pre-wrap;"> No (fix requires product change)</span>

---

### Description

<span style="white-space: pre-wrap;">The application returns an </span>**HTTP 500 Internal Server Error**, indicating an unhandled exception or logic failure inside the Finmars application.

<span style="white-space: pre-wrap;">In most cases, this represents a </span>**software defect**<span style="white-space: pre-wrap;"> rather than an infrastructure or configuration issue.</span>

---

### Typical Symptoms

- API requests returning HTTP 500
- Application stack traces in logs
- Errors reproducible with the same input
- No corresponding infrastructure or resource alerts

---

### Primary Meaning

A 500 error usually means:

- the request reached the application correctly
- the application failed while processing it

This class of error cannot be reliably resolved through operational actions alone.

---

### Required Action

#### Register an Issue in Finmars Core Repository

All confirmed 500 errors should be reported via GitHub:

<span style="white-space: pre-wrap;">🔗 </span>[**https://github.com/finmars-platform/finmars-core/issues**](https://github.com/finmars-platform/finmars-core/issues)

When creating an issue, include:

- request details (endpoint, parameters)
- error messages or stack traces
- timestamps
- environment details

---

### Resolution Path

- Issue is analyzed by Finmars maintainers
- Fix is implemented in the product codebase
- <span style="white-space: pre-wrap;">Resolution is delivered via a </span>**new Finmars release**

Customers must upgrade to the fixed version to resolve the issue.

---

### Urgency Handling

- **Most urgent bugs**<span style="white-space: pre-wrap;"> are addressed in </span>**best-effort time**
- Priority depends on severity, reproducibility, and impact
- No guaranteed fix timelines are implied

---

### Estimated Recovery Time

Not predictable  
Depends on investigation complexity and release cycle

---

### Preventive Notes

- Keep Finmars versions up to date
- Monitor application logs for early signals
- Avoid unsupported customizations where possible

---

### Responsibility Boundary

Finmars SCSA provides guidance, triage assistance, and escalation support.  
Bug fixes require product changes and fall outside standard operational support.

---