OptionalreplaySince?: TimestampUnset (the default): the subscription starts at each topic's tail; what was published before it opened is not delivered. Set: before the live messages, every entry each topic's stream still retains from this time on (the stream's own clock) is delivered first, oldest first, and a live message already replayed is not delivered twice (matched by CloudEvent id). For low-rate topics that must not lose a message across a resubscription, such as a worker's command topic while the worker moves to another pod. Needs the Redis pub/sub backend with PubsubRedisHost configured (FAILED_PRECONDITION otherwise); more retained entries than the gateway's PubsubReplayMaxEntries (default 10000), or more payload bytes than PubsubReplayMaxBytes (default 64 MiB), is OUT_OF_RANGE. Refusals come before the response headers.
With replay_since: deliver only the retained entries, then end the call (OK); no live subscription is opened. For a subscriber that already receives the topic live and needs only what it missed before (the WorkManager Runtime catching a moved worker up on its input topics). Without replay_since: INVALID_ARGUMENT.