We have a set of rules that work for our current login flow. I understand that actions run after rules. I have written a post-login action that to add some things to our tokens after the rules are done. My problem is that the action does not appear to run, though all of the rules do. Is there anything rules might do that will allow logins to be successful, but prevent an post-login action from running?
Here is some additional information in case it might be helpful:
- I believe that the action is not running because it begins by logging a message to the console, but nothing appears in the Action logs. Output from the rules appears in the Real-time Webtask Logs, but nothing from the action. Immediately after logging output, the action calls the api to set a custom id and access payload field, but those do not appear in the generated token.
- When I look at the top of the Custom Actions page, I see “Action is up to date” and “Login / Post Login, Runtime: Node 18 BETA (Not Recommended)”. Below that is “Upgrade this action from the Node 18 Beta to Node 18 GA runtime.” I have tried clicking on the update link, but it does not help.