After an Events rule matches, what is the service’s responsibility versus the destination’s, and how should multi-step follow-up be designed?
Select an answer to reveal the explanation.
Short Explanation
Events matches and delivers; the Function, topic, or stream then does what you configured. It is not a workflow engine that waits on a Function’s return to pick step two—put chaining inside the function or on a later resource-change rule.
Full Explanation
Official how-it-works: when the filter matches, Events delivers the event payload to each named destination; that destination performs its configured behavior (invoke, publish, append). Events is not an orchestrator or step-function product and does not wait on Function output to decide further platform steps. Design multi-step logic inside the function or with subsequent Events rules on later emissions.