One topic, separate consumers
A fictional receipt topic serves an archive consumer and a notification consumer. Each subscription has its own acknowledgment state. Completing one consumer’s delivery does not establish that the other finished. Use the topics lesson to inspect the local fan-out. The acknowledgment lesson then separates a pulled delivery from an acknowledged one. Use the returned acknowledgment ID for that pending delivery.
A crash after the commit
If a consumer commits a receipt and crashes before acknowledgment, a retry must not repeat the business side effect. Explain a stable business key and durable deduplication, rather than treating a messaging label as an exactly-once application guarantee.
The local adapter stores deterministic message records. It doesn’t run handlers or reproduce real acknowledgment deadlines, retry timing or every delivery mode. Continue in the Google Cloud course and verify real subscriber failure cases in an authorized environment.