AI Automators: Observation when using tokens in Advanced (Token)

The current user tokens should be automatically turned into their values from the logged in user as part of the token generation process: the most obvious thing to check is that there is a currently logged in user at the point that the AI request is being sent: if it's being trggered by the anonymous user (such as if you are running it via the queued process rather than directly) there will be no value. The other thing to check is that the user triggering the update has that value set on their account.

Thanks @mrdalesmith → , exactly what I thought but they are not.

I understand correctly then they should being interpreted but they are definitely not being.

All the Node entity-related are being interpreted as you would expect.

On the face of it, all of this testing is being done by UID:1 since I am logged so permissions ought not to be related however, to give more detail here, I will add that I am triggering the Automator through an ECA using the feature provided by ECA Integration module so I suspect that might well be the issue.

I can look into that further by using the ECA Switch User feature inside the ECA.

Yeah I'd recommend forcing ECA to use the root account as an initial test: I'm not 100% familiar with ECA but I wouldn't be surprised if it runs its integrations as anonymous in most cases.

@sirclickalot I tried user tokens with Advanced mode, those are working properly. It could be a possibility that your token itself is returning empty/null values. However, I have checked it on 1.1.xversion.