- Issue created by @SirClickALot
- 🇮🇳India anjaliprasannan
@sirclickalot Can you give more precise steps to reproduce the issue?
Hi all, I have been using the ECA / AI Automator alliance with recently trigger an AI Automator which is tied to a particular Long text field in a node entity.
Basic usage and it works nicely.
My ECA model responds to a node update event, the Automator is called, and everything works robustly and reliably.
The node ID used by the Automator is simply being picked up form the magic one 'implied' by ECA Update event - the good old [entity]
equivalent which never needs to be said explicitly.
It just works.
HOWEVER, I seem to be having trouble when I want to the trigger THE SAME Automator on a specified node ID but time, the Automator is invoked from a different ECA model that responds to a path (URL) request.
I have set up another ECA which uses an ECA Endpoint event to respond to /eca/node/automark?nid=NNN
.
I then pick of the node ID from the query string and stuff it in token which I named: targeted_id
.
I know for sure that all this works because I have debugged the life out of it!
So, to my mind, the next step is to simply call that same AI Automator from within my new ECA model which on the face of it look trivially simple to do.
As I understand it, I should simply need to 'send over' the NID I'm interested in as illustrated on the screenshot below.
(I appreciate that a screenshot only tells what it shows but it seems like the clearest way to illustrate the scenario and I can assure any reader that the gabbing of the nid
from the query string part all works perfectly.)
When I trigger this second ECA model into action by visiting the URL, all seems well but then I hit a WSD.
Digging into that reveals...
[19-Apr-2025 11:48:38 UTC] Uncaught PHP Exception Error: "Call to a member function getEntityTypeId() on null" at C:\Users\nick\Sites\bit-by-bit.org\public_html\modules\contrib\ai\modules\ai_eca\src\Plugin\Action\AiAutomatorRule.php line 77
This is telling me that the AI Automator is not receiving the NID.
So, in summary, what I am trying to understand is simple - is my thinking and my pattern of use correct?
Might this actually be a issue to raise on the ECA module itself?
Thanks all
Active
1.0
AI Automators
@sirclickalot Can you give more precise steps to reproduce the issue?