Apex Code Development You need to sign in to do that
Don't have an account?
indy Troubleshoot Platform Event in Production Environment
We have an existing implementation where Flow 1 publishes the event and Flow 2 subscribes to the same event and processes the apex logic. The apex logic includes callout and updating the Lead. Out of 1000+ data in production, a handful of records are not subscribed by Flow 2(or not published by Flow 1).
part of troubleshooting, we came to know that -
It is obvious that either Flow 1 is not published the event or Flow 2 is not subscribed to the event. But we don't have any technical way to prove that. How to draw the conclusion or troubleshoot or provide proof for these issues, especially in production.
Enabling the debug logs for user/automation users is not an option now, as it is eating the space within seconds.
part of troubleshooting, we came to know that -
- It is not a permission issue. other successful records were published by the same users.
- It is not a callout issue as well. The callout system doesn't have any log entries.
It is obvious that either Flow 1 is not published the event or Flow 2 is not subscribed to the event. But we don't have any technical way to prove that. How to draw the conclusion or troubleshoot or provide proof for these issues, especially in production.
Enabling the debug logs for user/automation users is not an option now, as it is eating the space within seconds.
Would suggest to check below reference for Considerations for Defining and Publishing Platform Events.
https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_considerations.htm
Thanks,