|
gmkws
|
September 27, 2019 at 10:46 am
This just started this mornig, for the last week meesage have been sent out.
Today all message are getting this error.
This is different from the test message issue.
Message failed to generate for the following reasons:
Incoming data for the Gateways data handler must have an EE_Transaction object as the value for the first array index.
|
|
Tony
|
September 27, 2019 at 10:57 am
That can happen if the data used to generate the messages is no longer valid, which can happen if you get a fatal error during a batch process, like in your other thread.
You’ll need to wipe the current messages queued for generation and retrigger those, whilst the other issues is investigated you may be better switching to send messages on the same request:
Event Espresso -> Messages -> Settings
Set ‘Generate and send messages’ to ‘On same request’
That will send the messages on the same request that triggered them rather than queing them up.
|
|
gmkws
|
September 27, 2019 at 11:00 am
The issue with the test messages is working now? but this issue just was reported to me a few minutes ago, those messages are all in red.
|
|
Tony
|
September 27, 2019 at 11:04 am
The issue with the test messages is working now?
I’m not sure if that is a question? If so, I’m not sure what it means.
If that test email caused a fatal on a batch process, it can invalidate the data used for that batch, meaning you’ll get the above when they try to process.
but this issue just was reported to me a few minutes ago, those messages are all in red
Which emails are red?
|
|
gmkws
|
September 27, 2019 at 11:08 am
I found a thread in EE that references the same email “farfaraway@galaxy.sp”
Seems it is some sort of core emails for testing?
https://eventespresso.com/topic/spurious-batch-messages/
|
|
Tony
|
September 27, 2019 at 11:12 am
I found a thread in EE that references the same email “farfaraway@galaxy.sp”
Seems it is some sort of core emails for testing?
Yes, thats correct but I’m not sure how that relates?
|
