A timeout limits how long a saga step waits for a participant’s response. It can help a system command meet its execution-time SLO, but a missing response does not prove that the step failed. section 9.2.3
Order creation and credit reservation
If Customer Service does not respond to reserveCredit() within the chosen interval, the Create Order Saga can treat the step as failed and reject the order. Because credit may already have been reserved, it must also send cancelReserveCredit() to preserve consistency. section 9.2.3
Use a timeout when bounded execution matters, and pair it with coordination that handles the possibility that the operation succeeded despite the missing response. Waiting indefinitely may let sagas complete eventually, but can miss the command’s SLO. section 9.2.3
