Hi. I'm using the C&P Gateway for WooCommerce and have been experiencing erratic behavior with orders. A few failed today.
Here is an error code posted in my WooCommerce order backend:
Click & Pledge payment failed (Transaction ID: ). Payment was rejected due to an error: “The ‘urn:APISchema.xsd:IPAddress’ element is invalid – The value ‘2a02:1205:34f6:c420:e40d:59bf:4cac:2494’ is invalid according to its datatype ‘NormalizedString’ – The actual length is greater than the MaxLength value.”.
and then 90 minutes later, this got posted in the same order:
Unpaid order cancelled – time limit reached. Order status changed from Pending Payment to Cancelled.
The user told me he tried a few different browsers with no luck. There was no corresponding C&P data record for this.
A few days ago, this order failed with this error (and there have been intervening successful orders):
Click & Pledge payment failed (Transaction ID: ). Payment was rejected due to an error: “The ‘urn:APISchema.xsd:IPAddress’ element is invalid – The value ‘2602:0306:3890:1730:18f2:bb4f:821c:dbc9’ is invalid according to its datatype ‘NormalizedString’ – The actual length is greater than the MaxLength value.”.
AND EARLIER - IS THIS RELATED?...
There was another attempted donation that did get through to C&P data record. This does not appear in my WooCommerce orders - but here is the error code that was posted along with the record:
Upsert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, npo02.OpportunityRollup: execution of AfterInsert
caused by: System.AsyncException: Future method cannot be called from a future or batch method: npo02.OpportunityRollups.rollupContactsandHousehol dsForTrigger(Set<Id>)
(npo02)
: []
Here is the beginning of the XML in C&P data (obviously not woocommerce)"
<?xml version="1.0" encoding="UTF-8"?>
<CnPTransactionData><Version>40</Version>
<Application><ID>CnP_FaaS</ID>
<Name>CnP_FaaS</Name>
<Version>FaaS.20140930.001.036.001.000.036</Version>
</Application>
The C&P Data ID: Transaction-2564
I've granted access in salesforece to look around.
Thanks
Here is an error code posted in my WooCommerce order backend:
Click & Pledge payment failed (Transaction ID: ). Payment was rejected due to an error: “The ‘urn:APISchema.xsd:IPAddress’ element is invalid – The value ‘2a02:1205:34f6:c420:e40d:59bf:4cac:2494’ is invalid according to its datatype ‘NormalizedString’ – The actual length is greater than the MaxLength value.”.
and then 90 minutes later, this got posted in the same order:
Unpaid order cancelled – time limit reached. Order status changed from Pending Payment to Cancelled.
The user told me he tried a few different browsers with no luck. There was no corresponding C&P data record for this.
A few days ago, this order failed with this error (and there have been intervening successful orders):
Click & Pledge payment failed (Transaction ID: ). Payment was rejected due to an error: “The ‘urn:APISchema.xsd:IPAddress’ element is invalid – The value ‘2602:0306:3890:1730:18f2:bb4f:821c:dbc9’ is invalid according to its datatype ‘NormalizedString’ – The actual length is greater than the MaxLength value.”.
AND EARLIER - IS THIS RELATED?...
There was another attempted donation that did get through to C&P data record. This does not appear in my WooCommerce orders - but here is the error code that was posted along with the record:
Upsert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, npo02.OpportunityRollup: execution of AfterInsert
caused by: System.AsyncException: Future method cannot be called from a future or batch method: npo02.OpportunityRollups.rollupContactsandHousehol dsForTrigger(Set<Id>)
(npo02)
: []
Here is the beginning of the XML in C&P data (obviously not woocommerce)"
<?xml version="1.0" encoding="UTF-8"?>
<CnPTransactionData><Version>40</Version>
<Application><ID>CnP_FaaS</ID>
<Name>CnP_FaaS</Name>
<Version>FaaS.20140930.001.036.001.000.036</Version>
</Application>
The C&P Data ID: Transaction-2564
I've granted access in salesforece to look around.
Thanks
Comment