3

I'm following this Configure the User and Batch Size for Your Platform Event Trigger documentation taking this Tooling API REST option. The resulting PlatformEventSubscriberConfig record can be queried via the Developer Console with "Tooling API" checked.

(The lack of Setup UI here adds a bit of confusion.)

But while the Apex trigger was running for the "Automated Process" user, it is now not running. I chose the SA User as the subscriber so plenty of privileges. Any known gotchas here or ways to check the configuration further?

A second related question is does the "Automated Process" user subscription that was added by the platform by default (shown below) need to be suspended to avoid duplicated handling?

default subscription

Improve this question
1
  • 1
    Note: It is important to stop and restart the platform event trigger for the configuration to be activated.
    – pfrandsen
    Commented Oct 20, 2021 at 14:38

1 Answer 1

Reset to default
2

OK. I'm now seeing it working with a backlog of bell notifications but only one email notification showing up.

Seems like the "Automated Process" user got automatically shut off even though it is presented as still 'Running".

So either I was doing something crazy (most likely) or there may be some delay before these change take effect.

Improve this answer
1
  • 3
    Our team has also observed that the PlatformEventSubscriberConfig settings do not go into effect immediately. We've seen it take several hours before events show up as created by our specified user.
    – mmindenhall
    Commented Jul 2, 2021 at 16:39

You must log in to answer this question.

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