Transact Technical Issues

HTTP Times Out When Using Transact

Resolution

Verify the size of the request. Large requests might time out (we recommend no more than 10 contacts at a time).
Look for internal and external network problems.
If you do not receive a response envelope, do not resend the submission; contact Support.

Not Receiving Notification of Errors

Resolution

Make certain a Notification Email address has been set within (and is a valid email address).
Contact Client Support.

Transact Bad Campaign ID Notification Error

Resolution

A transactional message group campaign was not properly set up within. The campaign must be set to the correct type.
An mailing is not automated or active and assigned to the campaign.
If campaign was recently set up, Transact may not have fully synchronized with (it can take up to 10 minutes).

Transact Duplicate Emails Sent

Resolution

A transact batch request process may send duplicate mailings if a failure occurred in the middle of sending and the job restarted. This is normal and expected behavior and is safeguarded to have minimal resends.
Your system may be sending duplicate requests.

Transact Emails Not Sent

Resolution

Verify you have received a valid XML Response Document.
If not, verify your system is sending.
Contact Client Support.

Transact IP Address Errors

Resolution

An organization may be attempting to send requests without having configured the correct IP address.
Your system has changed its 'Send' IP address (see User's Guide for further details).
Permitted IP addresses may not have synched yet with (allow up to 10 minutes).

Transact Parsing Errors

Resolution

Input request is not a properly formatted XML or fails to conform to schema.
Embedded characters should be surrounded by CDATA tags. For example: