I'm trying to figure out why some fields not populated on a custom object when the status is updated. Before Update trigger logic is straightforward, when status is changed, populate a field. And it is working when record updated manually. But it doesn't work when record updated by Automated Process. The problem is that I don't know how it updates record, I only see in Activity History that it was updated by Automated Process. Maybe there are some cases when it ignores triggers?

1 Answer 1


Seems like there is a limitation to fire triggers, process builders, flows, and workflows on any database inserts or updates performed by the Automated Process user.Also,we have an existing idea which has been created for the same behavior.

  • this is only partially true; Automated Process user applies to Platform Events and all triggers ensuing from subscribing to the Platform Event will execute
    – cropredy
    Commented Aug 7, 2020 at 1:14
  • @cropredy what do you mean exacrly ?
    – Ben2pop
    Commented Oct 13, 2022 at 19:57
  • @Ben2pop - what I meant is that Platform Events with trigger subscribers will run, by default, as Automated Process user and those triggers will execute; there are other actions performed on the database by Automated Process user that don't fire triggers (an example of which is in the Idea mentioned by Shirisha).
    – cropredy
    Commented Oct 13, 2022 at 22:53
  • Is there a work around ?
    – Ben2pop
    Commented Oct 16, 2022 at 8:22

You must log in to answer this question.

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