What's broken, where, since when, and who owns it
Revo Control is the operating view for every approved connection, so two companies don't have to compare logs on a call to find out whose problem it is.
Open issues
Open
- What
- Book returned an unknown status
- Where
- Alpine Distribution → Corvane Travel, book
- Since
- Today 09:42 UTC
- Owner
- TravelRevo operator
- Next step
- Checking supplier reference. Do not retry yet.
trace tr_7c41ab
- 09:41:58Buyer request received: book, CT-48213, traveller[redacted]
- 09:42:28No response within the timeout. State set to UNKNOWN
- 09:42:28Automatic retry refused: outcome unknown
See what broke, where, since when and who owns the fix.
- 4
- answers on every issue: what, where, since when and who
- 1
- redacted trace from buyer request to seller response
- 0
- blind retries of a booking with unknown status
Open issues, on one connection list
Every line answers the same four questions and gives the next step.
| What's broken | Where | Since | Owner | Next step |
|---|---|---|---|---|
| Book returned an unknown status | WhereAlpine Distribution → Corvane Travel, book | SinceToday 09:42 UTC | OwnerTravelRevo operator | Next stepChecking supplier reference. Do not retry yet. |
| Search nearing the seller's rate limit | WhereAlpine Distribution → Corvane Travel, search | SinceToday 07:15 UTC | OwnerCorvane integration engineer | Next stepReduce search fan-out before the cap is hit. |
| Quote latency above the usual range | WhereKestrel Wholesale → Corvane Travel, quote | SinceYesterday 22:10 UTC | OwnerKestrel on-call engineer | Next stepCheck the recheck endpoint, trace tr_5be302. |
| Mapping snapshot behind the feed | WhereKestrel Wholesale, hotel mapping | Since27 Oct | OwnerMapping analyst | Next stepReview changed records, then publish a new snapshot. |
Illustrative. Companies and data are fictional.
When a booking times out, nobody knows if it exists
The seller may have confirmed the room just as the connection dropped. Retrying could book it twice. These bookings go into their own queue, and the seller's status gets checked before anyone acts.
Booking status unknown
- Reference
- CT-48213
- Retry
- Blocked until reconciled
Unknown bookings
CT-48213
ALPINE · HT900
Unknown
Seller timed out on book. Status check in progress. Do not retry.
Owner: TravelRevo operator
CT-48190
ALPINE · HT205
CONFIRMED
The seller had the booking. Reference attached, and no second booking sent.
Owner: Corvane Travel to confirm with traveller
CT-48177
KESTREL · 40112
NOT FOUND
No record after repeated checks. The rebook decision goes to the buyer.
Owner: Corvane Travel
Illustrative. Companies and data are fictional.
- trace tr_7c41ab
- 09:41:58Buyer request received: book, CT-48213, traveller [redacted]
- 09:41:58Sent to Alpine: ALPINE · HT900, native rate code kept, credentials [redacted]
- 09:42:28No response within the timeout. State set to UNKNOWN
- 09:42:28Automatic retry refused: outcome unknown
- 09:42:43Status check by reference: no answer yet
Illustrative. Companies and data are fictional.
One redacted trace, read by both teams
This is the booking at the top of the queue. Native codes stay readable because engineers need them. Traveller details are removed before anything is stored.
What it does
Starts from the connection
One status page per connection carries recent test results, the last approved mapping snapshot, and errors split by search, quote and book.
Warns on seller limits
A connection approaching its rate limit raises a warning to a named owner, while there's still time to reduce traffic.
Follows one request across both companies
A correlation ID stays with the request from buyer to seller, with credentials and traveller data removed, so both teams read the same trace.
What it covers, and what it leaves out
The list on the right is deliberate, and we'll say when any of it changes.
Included
- A status page for each approved connection
- Redacted error breakdown for search, quote and book
- Latency by adapter and partner
- An unknown-booking queue, reconciled against the seller
- Seller rate-limit warnings
- A named owner on every blocker
Deliberately left out
- Long-term analytics and customisable dashboards
- Commercial settlement reconciliation
- Automated traffic or routing decisions
- Financial forecasting
Do you offer an uptime commitment or a support SLA?
No. We don't offer an uptime commitment or a support SLA, and we won't quote a figure we haven't measured.
Who can see a trace?
The two companies on that connection, and our operators when diagnosing an issue. Traces exclude traveller data, payment data and credentials, and support staff can't reveal stored secrets.
Does Revo Control fix a booking for us?
It checks status and tells the owner what it found. Rebooking or cancelling stays a decision for the buyer and seller, and no automated process does it for them.
Does it replace our own monitoring?
No. It covers what happens across a connection, between your systems and your partner's. Keep monitoring your own platform as you do today.
Questions we'd ask too
Straight answers, including where the answer is no.
Who gets paged when a partner connection breaks?
If it's you, tell us what you need to see at that moment.