Cool - the data is indeed being recorded! And you are clearly right, for some reason the automation is no longer functioning / triggering for you. No need to turn off approvals.
I was about to implement something similar using this plugin - will let you know if I can repro the problem.
Also - perhaps these last 8 replies should be moved to Bug?
We had moved them to a new bug topic but I moved it back here.
Seems there are two problems currently intermingling - @EloiseBarrege has been having a problem with automations that create badges, starting with this post back in October. It seems to be a configuration issue specific to the site. Eloise, if you are not able to fix it I recommend you start a new topic in Marketplace to find someone to help you fix it.
@Paul_King seems to be struggling with a different issue, that an automation that previously worked stopped working after an update. If it persists and @nathank is able to repro, can one of you two start a new Bug topic to explore that further?
Below are what I hope are the relevant screenshots
There are two groups I am dividing my users into: ‘Private Forum User’ or ‘Public Forum User’.
A user must select one of these by name when signing up, from a dropdown custom user variable called ‘Forum Access Level’.
When they complete their signup correctly and are approved, the Automation plugin then fails to put them into either of those groups, no matter what group they chose.
The result for all new approved user profiles is as below (the group setting remains unpopulated, until I manually set it to one or both of the groups myself)
Is it possible to create and register our own trigger for our custom automation? Is there any document steps/samples for it? I’m trying to create a “accepted_solutions“ trigger, the “first_accepted_solutions“ is not fit to my use case since I’m would like the automation to be triggered for every single post marked as solution.
How are params supposed to be entered for automated Data Explorer queries? The relationship between the data explorer param and the key/value pair in the edit query params popup isn’t clear to me.
I was running into this as well, and the solution was to disable “Automatically set as primary group” on the groups that are part of the dropdown. If you don’t need to set a group as their primary group, this may be a fine workaround. For myself… it’s not. We’d like to use a dropdown to select a primary group. The error I’m seeing in sidekiq seems to be related to how the users are parsed, with missing attribute ‘staged’ for User showing.