Mobile App Transactionals

[deezone]

Transactional email messages triggered by the mobile application are not resulting in the expected email messages.

The request process is Mobile App -> NorthStar (UserAPI) -> Drupal API -> Message Broker. Somewhere in this flow the needed values are not being passed to result in a complete request to Message Broker.

Issue Summary:

• user_registration: Message not sent
• user_password: Message not sent
• campaign_signup: working as expected.
• campaign_reportback: *|CAMPAIGN_TITLE|*merge_var` is not set.
• Incomplete user document in mb-user database (used to generate digest messages).

Example Incomplete User Document in mb-user Database:

Darren "Dee" Lee [20:28] via Slack
@aaron: An example of a "funky" payload passing through Message Broker:

{
"_id" : ObjectId("565c96b0d86f5ff3f7341316"),
"email" : "don.draper+201511301024@dosomething.org",
"created" : ISODate("2015-11-30T18:26:17.350Z"),
"subscribed" : 1,
"campaigns" : [
{
"reportback" : ISODate("2015-11-30T18:26:41Z"),
"signup" : ISODate("2015-11-30T18:26:17Z"),
"nid" : 1503,
"_id" : ObjectId("565c94c935f7e1ad3e52221f")
}
]
}

This is flagged because there's no drupal_uid.

Searching the Drupal app for "don.draper+201511301024@dosomething.org" is not found and yet
the user is signed up for a campaign?

Does this look DS Mobile App related?

---

Aaron Schachter [11:10] via Slack
@dee to answer your question from last night - yes that’s a test user i’ve been using in the mobile
app. i’ve been testing mostly on staging. when we create users in northstar by passing
create_drupal_user=1" into the query string which should create the account. but perhaps one of
the northstar endpoints is not sending the right data to the relevant phoenix reportback endpoint.
https://dosomething.slack.com/archives/phoenix/p1448933281001311

Related / Duplicate:

• Mobile App Merge Tag Bug #5870

[deezone]

Note to self:

• User registration: dlee@dosomething.org, 347xxxzzzz
  • no transactional received.
• Second user registration: dlee+mobileApp-151203-01@dosomething.org
  • no transactional email received
  • no log entry for dlee+mobileApp-151203-01@dosomething.org in Mandrill or mbc-transactional-email.

Assumptions:

• A call from the mobile app is made to the userAPI (Northstar) to create a Drupal user. Existing user does not produce transactional email?
• Logout of app allows new user registration, "+" in registration email is seen as different user?

Questions:

• Where to look at mobileApp and userAPI logs for user registrations? Looking for entries for dlee@dosomehting.org and dlee+mobileApp-151203-01@dosomething.org.
• A call from the mobile app is made to the userAPI (Northstar) to create a Drupal user. Existing user does not produce transactional email?

cc @jonuy @angaither @aaronschachter - comments to questions?

[aaronschachter]

Just replicated the reportback bug getting a CAMPAIGN TITLE email on staging: It was a PBJ Slam reportback transactional for aschachter+20151207@dosomething.org

@deezone Yes - no emails for an existing user. Not sure where / who should be looking into the user registration emails issue.

[aaronschachter]

Same email (missing the title merge tag) when reporting back with the same user for Mirror Messages.

[aaronschachter]

Also worth noting the Signup transactionals I received for these two campaigns worked ok -- the Campaign title was displayed properly in the copy

[deezone]

@aaronschachter Any comments to address the outstanding "Question" above?

Where to look at mobileApp and userAPI logs for user registrations? Looking for entries
for dlee@dosomehting.org and dlee+mobileApp-151203-01@dosomething.org.

#5872 (comment)

[jonuy]

@deezone

Where to look at mobileApp and userAPI logs for user registrations?

I don't think there are any easily accessible logs at least to see. Would ssh'ing into the mongo db itself and checking out the documents there be enough? What sort of info are you interested in finding?

Existing user does not produce transactional email?

If we've got the user in Northstar and that user's already got an assigned Drupal id (which I suspect should be the case in a majority of these scenarios) we don't forward the call onto Phoenix. So yea, I can see in that scenario transactional emails not getting sent. I'm not sure though about the case where there's a user that exists on Phoenix but not on Northstar. Do we want to send a transactional if a user's account had already existed?

[deezone]

@jonuy vv ?

Would ssh'ing into the mongo db itself and checking out the documents there be enough?

Queries on the Mongo db would work.

What's the Mongo server and db name? I seem to only be able to get at mongo4 for the Message Broker stuff. Perhaps I need more rights once I know where to look. What Mongo server do you use for the mobile app / Northstar?

[deezone]

Thanks @jonuy , my response and question for perhaps you or @aaronschachter :

If we've got the user in Northstar and that user's already got an assigned Drupal id (which I
suspect should be the case in a majority of these scenarios) we don't forward the call onto Phoenix.

That makes sense.

What about user password resets? The transactional email that provides a reset link in an email is not sent. Does that make sense in the case of the app? Can you reset your password via the mobileApp or perhaps that's on the roadmap?

[aaronschachter]

On the roadmap for version WayLater -- right now we direct users to the web in order to reset password.