Transaction identifiers for transactions are managed to mitigate potential mismatches that may occur in the event a message associated with the transaction is not delivered to the intended destination. For example, in the event an access terminal accepts a bearer context request, the access terminal may not immediately release the transaction identifier associated with that transaction. In this way, in the event the access terminal receives a second bearer context request associated with that same transaction identifier (e.g., due to the accept message not reaching the network), the access terminal may send a second accept message in response to the second bearer context request.