SAP BTP
The destination certificate expired
A business-critical BTP connection starts failing after a certificate rollover. Rehearse evidence gathering, ownership and a controlled restoration.
20 minutes suggested · Four incident updates · One shared screen
Start this rehearsal →Watch the quick field guide
24-second visual guide · captions and transcript · no autoplay
Read the guidance transcript
Spot the symptom. A failed connection does not prove the cause. Read the simulated destination, identity or integration evidence first.
Keep uncertainty visible. Certificates, credentials and authorizations have different owners. Decide which evidence you need before a change.
Discuss the trade-off. Compare a controlled recovery, a broad change and waiting for more information. Watch how the fictional story responds.
Make the next incident easier. Agree who owns the dependency and how it is monitored. Record actions; no real SAP tenant is changed.
Who should be in the room?
Facilitator, BTP platform owner, Integration lead, Business process owner. These are discussion roles, not account invitations. One person records while the team talks.
What the team will practice
The invoice flow stops
A failed connection is confirmed. The cause has not been established.
Discussion: Which evidence and owners do you bring together before changing the destination?
Two certificates, one unclear owner
The team has a plausible dependency gap, not proof that every failure has the same cause.
Discussion: How would you authorize and verify a scoped recovery without changing unrelated destinations?
Finance wants the backlog released
A green connection alone does not establish that replay is safe or that duplicates cannot occur.
Discussion: Who owns replay approval, reconciliation and the business update?
The first test succeeds
The rehearsal has reached a recovery checkpoint, not a proven production recovery.
Discussion: What evidence would you need to close the incident and prevent the ownership gap recurring?
What you’ll leave with
Your own recorded decisions, uncertainties and improvement actions with owners, dates and status. Print a readable report or export a browser-local session to revisit.
Original fictional content, not a technical response procedure. No real systems are changed. This exercise does not certify security readiness or compliance.
Read the facilitator guide →