# Why does message parsing fail?

## Message parsing failed

After you setup integrations on Spike.sh, these integrations send us payload of JSON data for every new incident. We convert this JSON data into a human-readable format which is then used on the [incidents table](https://app.spike.sh/incidents) and in phone calls, emails, Slack etc.

Sometimes, this parsing fails and your table might see an entry like below -

![Example of incident message parsing fail](/files/-MHEmlvh45Ej43hGqFwj)

### Report with a single click

When you see this, please report this issue to us so we can start looking into this. The more you report the better this parsing gets.

![Report with a single click](/files/-MHEqboZPW6BHzinoRrw)

### Why does this happen?

We try our best to parse all the payloads and convert it into a gist you can actually read and get a sense of the incident. Each integration has tons of cases and our parser fails to understand it and that's what causes Incident message parsing fail.

### Does it affect my alerts?

Yes, your alerts will not have the message.

### Would I still receive alerts?

Yes. Alerts will still be sent however the exact incident message will not be available.

### Is the incident affected?

No. The details of your incident are still available. You can click on the #ID of the incident and see all the details as you do with other incidents.

### Should we take any action?

We would love it if you can please report the incident.

{% hint style="warning" %}
Once the parser is fixed, it will not change the message for existing incidents but it will surely pave the way for future incidents
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.spike.sh/incidents/why-does-message-parsing-fail.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.