This is an old thread but a new problem for me. I have several AA's firing off a newly-confirmed user. However, one of them is geocoding the address, the time to do which varies. Further down the line, an email gets sent with that geocoded address. It appears most of the time, that address is blank and does not appear in the email.
So this is a case where it would be better if one AA could be daisy-chained off another; in this case, sending that email needs to wait for the address geocoding to finish. Is there a way to do that? I think that would solve the problem.
Your issue however can likely be solved by using the Reload User parameter under the Parameters tab so it'll reload the user object. Example as to why this is needed as follows.
Action 1 <- changes field cb_test to 123
Action 2 <- checkes for cb_test being equal to 123
In the above if both are acting on the same trigger Action 2 will fail. The reason is because they're both acting on the same non-referenced user object. So Action 2 won't see the changes made by Action 1. The workarounds to this is to either specify the user object variable as a reference variable or to enabled Reload User in Action 2 (not necessary for Action 1) so that it reloads the user object.
Kyle (Krileon) Community Builder Team Member Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
-- If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
-- If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
-- Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
-- My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
I did try the Reload User option, but it didn't work. These geocode API queries take about 1 second to complete, so I believe the chaining option is necessary in this case. Thanks for the link! I will try that tonight. Like I said, the geocoding is definitely working. I can check the profile of the person whose welcome email didn't have it and it's in the profile. So this really seems like a timing issue.