I know events are processed asynchronously in the subscriber. Currently we have a flow that creates an event (and publish it), We are creating a trigger that listens to that event and invokes a http call-out per each event. My question is - can we assume that the trigger batch will 1 every time - because the change that invokes the flow (and publish the event) is manually from the UI. Are events gathered up to the event bus and then processed together in the subscriber or can we rely that if one event was created in the publishing transaction, then we will have one event in the subscription transaction?

  • I have seen events fired in different transaction run in batch – Pranay Jaiswal Apr 22 at 5:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.