Send failures that name the step and give you a reference

If a send fails, the message names which stage failed and gives a short reference the admin can find in the logs.

What it is

Every send carries a short correlation id stamped into both the server log line and the error response, plus a step marker tracking how far the handler got — auth, parse body, hash password, insert link, insert overrides, build URL, audit log.

Also called: couldn't send the estimate · error sending · what went wrong

See it
Send failures that name the step and give you a reference
CustomerBuildingAmountStatus
Gideon Alt30×40 Garage$1,580Approved
Delia YoderEquipment Storage$14,690Sent
Gideon AltHobby Shop$2,340Draft
Delia Yoder30×40 Garage$15,070Paid
Delia YoderRiding Arena$6,330Paid
The send-error state in the modal showing the message, the step and the reference code. Sample data — no customer information appears here.
How it works
  1. 1A reference id is generated at the start of the request.
  2. 2Each stage assigns a step marker before attempting work that can throw.
  3. 3The failure response carries the user-facing summary, the underlying technical detail, the step and the reference.
  4. 4The same reference appears in the server log line for that request.
Why we built it

A failed send said 'Internal server error', which tells the builder nothing and gives whoever they call nothing to search for. Failures now name the stage that broke and hand back a short reference the builder can pass to an admin, who finds the matching line in the logs in seconds instead of reconstructing the send from scratch.

The problem
  • Opaque failures with no way to correlate a user report to a log line
Sound familiar?
What you get
A failure you can report in one sentence
Support can find the exact request

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →