Several downstream municipal services—and a short replay window—must all see the same OCI resource-state change that an Events rule matches. Which action destination fits that fan-out?

When several downstream municipal services—and a short replay window—must all see the same OCI resource-state change that an Events rule matches, deliver the match to a Streaming stream action. The rule still filters the CloudEvent; Streaming then holds the record so multiple consumers can read independently and rewind within retention. That fan-out-plus-replay shape is why Streaming is the Events destination for shared observation of one emission. A single Function action only, because Streaming cannot receive Events deliveries, is wrong on both counts: Streaming is a documented Events action, and a lone Function is appropriate when one worker should handle the match—not when many readers need the same event. An OCI Queue action for multi-reader replay fails because Queue is not a documented Events destination and its consume-and-delete model is a poor fit for multi-consumer replay. Embedding the event in a Vault secret version so every service polls secrets invents a side channel that is neither secure practice for event fan-out nor an Events action. Exam caveat: Streaming retention still applies after Events delivery—consumers that lag beyond retention lose the event even though the original OCI resource change already happened. Operational check: configure the rule’s Streaming action, emit a test resource change, and verify two independent consumer groups can read the same record at different times within retention.