Update. Been playing around and learned, it is not the trigger inputs.
The issue (flow not triggering from api) is only apparent when I added a new "List rows" action.
So I'm afraid, the title is now miss-leading.
However, it may help someone else. The issue still exist. Just not a trigger issue.
The issue now is, why did adding a list rows disable the trigger. I did check permissions on the entity for the list rows.
Seems like the flow is doing some kind of "pre-flight" check. If fails, no trigger.
Flow triggers and runs without the list rows. I tested the list rows on its own. Copying the list rows action and pasting into another new flow, runs fine.
So it's a combination of the contents of my flow, with the addition of the list rows.
And permissions are set on list rows entity.
Clues how they may be interferring?
NOTE: The list rows action does NOT reference any tokens/variables and is NOT referenced by anything else (yet).
Thanks,
Doug
