3

Consider this scenario. I have a trigger on Platform event named as SOject_Upsert_Data__e

trigger SObjectUpsertData on SOject_Upsert_Data__e (after insert) {
    // Some Logic
}

And I am raising Platform events from flows wherever I need to update any record in salesforce. The reason is because to better capture Lock row exceptions and retry them. And also we have many flows, like (1000) and have made it very complex unnecessary. So a cleanup is very hard and very time consuming and many issues occurs because of lock row.

Question: There might be more than 50K requests coming to the triggers in 24 hour period. So my doubt is does 50K limit applies here too? And whats the difference between Event Delivery and Event Publishing, and under which event does triggers fall?

enter image description here

2 Answers 2

5

You should really link to the docs you reference. Here's what I believe to be the relevant passage:

Non-CometD clients, including Apex triggers, processes, and flows, don’t count against the event delivery limit. The number of event messages that an Apex trigger, process, or flow can process depends on how long the processing takes for each subscriber. The longer the processing time, the longer it takes for the subscriber to reach the tip of the event stream.

Note that most discussion of limitations within that link discusses CometD subscribers, which are not what you are using.

5

Event Delivery refers to CometD subscribers such as:

  • Lightning Web Components that use lightning-emp-api to receive Platform Events
  • Visualforce pages that use a CometD implementation to subscribe to Platform Events, as in this example
  • External clients that use the Streaming API to receive events

Delivery of the Platform Event to a trigger does not count against the 50K limit.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .