Message Errors
The following Message (email/SMTP and SMS) errors have documented solutions.
- "Unable to read data from the transport connection:net_io_connectionclosed"
- This error can occur for multiple reasons, including when MinistryPlatform Messages send to SendGrid but you exceed the plan limit or have a bad API key. The Message is in the Action Text of the Recipient record.
- "Message cannot be sent: The operation has timed out."
- This error can occur for various reasons when the system can't reach the mail server or is interrupted. Possibly, the firewall is blocking outgoing connections on the port.
- "Message does not have "Subject." Message body is null."
- This error occurs when a you manually change a Communications_Message ("Recipient" records) with an Action Status of Sent (thus with a blank subject and body) to an Action Status of Ready to Send.
- "Message cannot be sent: Error in processing. The server response was: You've exceeded your messaging limits."
- This error can occur for various reasons. You may have a daily or hourly limit on your account, or a limit on the number of Messages that can send at one time. Check with your mail processor (usually SendGrid).
- "Attempt to send to unsubscribed recipient" / ERROR: 21610 in Twilio
- This error may display in the Action Text field on the Message Log tab of a Contact record. This indicates that the person you're trying to message has opted out of receiving messages. For details on the error, see this Twilio article. When an outbound text message responds with HTTP Status Code 400 and Error Code 21610, MinistryPlatform will look up the Contact and change the Do Not Text field to Yes.