Country or region and language

    Choose your country or region and your language.

    Suggested for you

      All countries and regions

        Choose your character

        It shows in the top bar and on your profile. Change it any time.

        Google Cloud Pub/Sub messages and acknowledgments

        Follow one published message into a subscription, then distinguish receiving the delivery from completing its business work.

        Checked 14 November 2026

        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.

        Sources

        Your Work Gym account

        Save your progress and pick up on another device. Your browser's progress comes with you.

        or

        You can keep practicing without an account.

        Help and feedback

        Ask a question, tell us what is not working, or share an idea. We reply by email.

        What is it about?

        We use it only to reply to you.