Developer documentation

MTProto service messages, acknowledgments and recovery

Understand RPC correlation, acknowledgments, salts and resends without confusing response cancellation with undoing an action.

GetTGAPI editorial teamUpdated
Documentation notesReviewed

Based on official sources and independently maintained by GetTGAPI. Documentation and glossary →

On this page
  1. Acknowledgments have protocol meaning
  2. Cancelling a response is not undoing execution
  3. Recovery recommendations

Acknowledgments have protocol meaning

RPC results correlate with request-message identifiers and may themselves need acknowledgment. Other service messages manage sessions, salts, timing and message state. They are not user chat messages.

Cancelling a response is not undoing execution

Dropping an RPC answer does not guarantee that an already-submitted business operation stops. Disconnecting also does not reliably cancel a send or payment. Separate an unknown result from a definite failure.

Recovery recommendations

Retain operation identity and known results, then reconcile after reconnecting. Let the protocol implementation handle timing, salts and sequence corrections according to the specific error.

Test processed requests with lost answers, duplicate responses, old-message resends and restarts. For financial or authorization actions, idempotency and reconciliation matter more than simply increasing retries.