Understand repeated failures without investigating them one by one.
Stored failures from files, events, jobs, or monitors go in. An issue group with an occurrence count, first and last seen times, and a sample comes out.
test
Events · destination hooks.example.com/orders
#1evt_8f1e · HTTP 500 Internal Server Error2m agoFailed
#2evt_8f20 · HTTP 500 Internal Server Error4m agoFailed
#3evt_8f21 · HTTP 500 Internal Server Error6m agoFailed
Each failed delivery stores the same error text. Investigating them one by one is the problem.
What it does
Real product states, not a promise.
Stored failures from files, events, jobs, or monitors go in. An issue group with an occurrence count, first and last seen times, and a sample comes out.
- Fingerprint groups matching errors
- Occurrence count, first and last seen
- Occurrences listed per issue
- A sample failure with its evidence
Input
Stored failures from files, events, jobs, or monitors
Output
An issue group and its occurrences
Where it fits
Where it fits
01
Failing webhook destinations
02
Recurring job errors
03
Flapping monitors
API example
One request.
GET /v1/issues/{fingerprint}. The full request and response contract is in Flowyn Docs.
AcceptedClaimedAttemptedTerminal state# GET /v1/issues/{fingerprint}
# Request and response: /docs/observe/issuesFrequently asked questions
Where is the exact request contract for Issues & diagnostics?
In Flowyn Docs and the OpenAPI document at https://api.flowyn.dev/openapi/v1.yaml. This page shows the request; the docs page lists every field, status value, error, and limit.
Does Flowyn fix the failing API?
No. Flowyn observes and reports. It records the failure, opens an incident, and tells you. It does not change your system.
How do heartbeats work?
You create a heartbeat monitor with an interval. Your process calls POST /v1/monitors/{id}/ping each run. If no ping arrives within twice the interval, the miss is recorded; three misses in a row open an incident.
Build with Issues & diagnostics.
Create a workspace, make your first call in the test environment, and inspect every attempt.