Support

Home Forums Event Espresso Premium Transaction emails not being sent

Transaction emails not being sent

Posted: May 16, 2018 at 3:18 pm


Bob Randklev

May 16, 2018 at 3:18 pm

For a couple weeks now our client has reported customers calling not getting their registration or payment confirmations. They also report the office is not getting the registration confirmation email either.

But we can see there are some people getting emails so it’s not broken just certain registrations?

We use Sendgrid via API for this site and I can confirm the emails are not getting to SendGrid …. but some are. So it’s not an SMTP or email provider problem.

I’m trying to put my finger on why some are being sent and others are not?

I found this in our error log and hope it helps:

[16-May-2018 21:11:54 UTC] —————————————————————————————-
[2018-05-16 21:11:54] Exception Details
Message: Incoming data for the Gateways data handler must have an EE_Transaction object as the value for the first array index.
Code: EE_Messages_Gateways_incoming_data – __construct – 51
File: /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/data_class/EE_Messages_Gateways_incoming_data.class.php
Line No: 51
Stack trace:
#0 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Generator.lib.php(919): EE_Messages_Gateways_incoming_data->__construct(Array)
#1 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Generator.lib.php(889): EE_Messages_Generator->_set_data_handler(Array, ‘EE_Messages_Gat…’)
#2 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Generator.lib.php(760): EE_Messages_Generator->_validate_and_setup_data()
#3 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Generator.lib.php(153): EE_Messages_Generator->_verify()
#4 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Processor.lib.php(124): EE_Messages_Generator->generate()
#5 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/modules/messages/EED_Messages.module.php(292): EE_Messages_Processor->batch_generate_from_queue()
#6 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/modules/messages/EED_Messages.module.php(259): EED_Messages->run_cron()
#7 [internal function]: EED_Messages->execute_batch_request(Object(WP_Query))
#8 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/core/EE_Module_Request_Router.core.php(240): call_user_func(Array, Object(WP_Query))
#9 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/core/EE_Module_Request_Router.core.php(184): EE_Module_Request_Router->_module_router(‘EED_Messages’, ‘execute_batch_r…’)
#10 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-content/plugins/event-espresso-core-reg/core/EE_Front_Controller.core.php(242): EE_Module_Request_Router->resolve_route(‘ee’, ‘msg_cron_trigge…’)
#11 [internal function]: EE_Front_Controller->pre_get_posts(Object(WP_Query))
#12 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-includes/class-wp-hook.php(286): call_user_func_array(Array, Array)
#13 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(”, Array)
#14 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-includes/plugin.php(515): WP_Hook->do_action(Array)
#15 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-includes/class-wp-query.php(1634): do_action_ref_array(‘pre_get_posts’, Array)
#16 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-includes/class-wp-query.php(3230): WP_Query->get_posts()
#17 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-includes/class-wp.php(599): WP_Query->query(Array)
#18 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-includes/class-wp.php(715): WP->query_posts()
#19 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-includes/functions.php(960): WP->main(”)
#20 /srv/users/serverpilot/apps/streetsmartsdriversed/public/wp-blog-header.php(16): wp()
#21 /srv/users/serverpilot/apps/streetsmartsdriversed/public/index.php(17): require(‘/srv/users/serv…’)
#22 {main}


Josh

  • Support Staff

May 16, 2018 at 3:38 pm

Hi Bob,

The “Incoming data for the Gateways data handler must have an EE_Transaction object as the value for the first array index” error can be avoided by going to Event Espresso > Messages > Message Settings and set the the option for emails to be sent on the same request.


Bob Randklev

May 16, 2018 at 3:43 pm

I see on the messages page there are 377 messages “Queued for Generating”

Searching the forums it talks about Cron jobs but we have a dedicated server running ServerPilot.

I don’t see any cron jobs in the list so why did this stop processing?

Is there a cron I should/could add to see if that solves the problem?


Tony

  • Support Staff

May 17, 2018 at 5:18 am

Searching the forums it talks about Cron jobs but we have a dedicated server running ServerPilot.

I don’t see any cron jobs in the list so why did this stop processing?

It uses WP Cron rather than actual cron jobs, so if you are checking for cron jobs on the server you wont find any for EE.

However the error Josh mentioend above:

Incoming data for the Gateways data handler must have an EE_Transaction object as the value for the first array index

Is usually caused by some kind of garbage collection on the server running at just the right time to clear out the transients that were used by the messages system, which then breaks the messages in the queue.

If you go Event Espresso > Messages > Message Settings and set the the option for emails to be sent on the same request it will prevent that from happening again as the messages are no longer queued and send immediately.

However that will not fix the broken events in the queue, those will need to removed and retriggered from within EE.


Bob Randklev

May 17, 2018 at 5:40 am

Ok I changed it to Same Request and the queue is not growing.

I’ve gone into the queue and choose 50 and clicked process and send
Queue Send

I then get this error:
error

I was able to process the first 100 or so but these are giving an error.

I’m not overly concerned about these as they are from a few days ago and I know after a class sold out the client downloads the registration info to manage offline and deletes the class registrations so this could be the problem.

But I wanted to share if it’s something else.


Josh

  • Support Staff

May 17, 2018 at 8:41 am

Yeah that could be a problem caused by deleting the associated registrations.

The support post ‘Transaction emails not being sent’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3

Documentation for Event Espresso 4

Status: closed

Updated by  Josh 2 months, 4 weeks ago ago

Topic Tags

Notifications

This topic is: not resolved
Do NOT follow this link or you will be banned from the site!