Find an execution
Search loaded execution IDs and filter by classification. Select a row to inspect its reported boundaries.
THE PRODUCT
Follow the evidence.
Understand the outcome.
Connect the delivery boundaries your application reports, from a PostgreSQL outbox through BullMQ to a customer webhook.
ONE DELIVERY PATH
From request
to external effect.
A committed transaction, a completed job, and a confirmed webhook effect answer different questions. Nestarc brings their reported evidence into one execution timeline.
- 01HTTP request
The application receives the request.
- 02PostgreSQL outbox
The transaction records the work to deliver.
- 03BullMQ worker
The job is enqueued and processed.
- 04Customer webhook
The request and external effect need their own evidence.
This is the supported workflow, not a live execution. Boundaries appear in the console only when reported, with explicitly labeled display projections where applicable.
LEARN THE DIFFERENCE
Four scenarios.
Different evidence.
Explore the same timeline and metadata inspector used in the dashboard. Start with an unknown webhook outcome, then compare it with a reported failure.
Sample executions
Choose an execution, then expand a timeline row to inspect its metadata.
Fixed sample times · UTC
These records are bundled with this page.
Execution sample-webhook-unknown
Webhook outcome unconfirmed
Last confirmed boundary: webhook request accepted
What remains unknown
A webhook request boundary was observed, but the external effect was not confirmed.
Investigation guide
- Observed facts
- The sender reported a timeout while waiting for the webhook response.
- What remains unknown
- The timeout does not establish whether the receiver applied the effect.
- Check next: Receiver / effect record
- Use your own mapping for this execution to find the receiver’s processing or effect record, if available. Compare the recorded attempt; an HTTP response alone is not that record.
Assessment evidence: Webhook request · Attempt 1Source occurred: Collector received:
Evidence timeline
6 observed eventsDisplay-only boundary · Not collected Evidence
Synthetic observations only. This preview does not verify a customer installation or a delivery. Missing evidence alone does not mean failure or an interrupted connector.
INSIDE THE WORKSPACE
A clearer next
investigation.
Read the timeline
See the last confirmed boundary alongside the explanation of what is known and what remains unknown.
Inspect the evidence
Expand an event to view allowed metadata, including source occurrence and collector receipt as separate times.
Keep context in view
Check when evidence was last received. Receipt freshness is a separate signal from the delivery outcome.
CONNECT YOUR DELIVERY PATH
Read your first timeline.
Create a workspace and connect your supported application in the free beta. Read the guide for installation and interpretation.