We automatically create an Opportunity when an Account is created as part of an after-insert Trigger on Account.
This all occurs in the after insert Account transaction, there are no @future or queueables involved.
Some of the fields that are set on the Opportunity as part of this are prone to frequent updates, so we moved that logic into a Process Builder. This PB is set to fire on create of Opportunity with no filter logic.
We have observed that when an Opportunity is created manually, the PB fires with no problem. However, when an Account is created and the Opportunities are created by the trigger (DML insert), the PB does not fire.
The PB is set to allow recursion.
So: is this by design? Any way to get the PB to fire on a DML-inserted record?
WF_CRITERIA_BEGIN
line with the name of the PB); @Brian Miller - I tried setting the PB to fire on create and edit and changing the criteria node to containISNEW()
only; this didn't work either. Thanks again.1. Have only one record-change process per object
2.For each object, use one automation tool.
So your issue could have been avoided if you followed any of the above.