Announcement

Collapse

Information Needed

See more
See less

Error Transactions not making it to Salesforce

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • CnP.Support
    replied
    Good day Eric Pitts

    We have reviewed the transaction and the following is the report of all the order numbers you had posted:

    The following had a date issue which we resolved and posted successfully:
    • 33189-1707251811523117425
    • 33189-1709122007274740237
    • 33189-1709261853242959787

    The following had returned an error due to a custom filter:
    • 33189-180416162030867
    Click image for larger version

Name:	CustomFilter.jpg
Views:	22
Size:	11.1 KB
ID:	39035

    The above filter returns an error for this post.


    Click image for larger version

Name:	Campaign-Filter.jpg
Views:	45
Size:	89.6 KB
ID:	39034


    The following show as posted with no issues & are all in your Salesforce instance already.
    • 33189-180417115240447
    • 33189-1804171323318402776
    • 33189-180417134145247
    We are also seeing a number of errors due to CPU limit exceeded. We have tried pushing the records but Salesforce CPU limit returns error. Please login to your instance and check this link:

    https://madd.my.salesforce.com/?ec=3...exTraces.apexp

    Please pay close attention to what is added to your instance. You have a very complex installation with many applications all acting on each of our posts. A number of triggers block our posts before we even take control of the posted data. For example, today we see the Order Number: 33189-1804181009070873019 does not post due to CPU error, as stated above. In reviewing the log file we see a lot of workflows running on these transactions. Salesforce does not let us post the transaction.

    Hope this helps.


    Leave a comment:


  • Eric Pitts
    replied
    Sounds great thanks for the update.

    Leave a comment:


  • CnP.LiveSupport.AB
    replied
    In the first 3 orders, the birthdate was entered as a date when the field was expecting date-time. With the other orders, the temporary contact record was deleted. I will review and let you know what further action may be taken.

    Leave a comment:


  • Eric Pitts
    replied
    Thanks for the update. Can you tell me which order number had that invalid date?

    Leave a comment:


  • CnP.LiveSupport.AB
    replied
    Hi Eric,

    So I looked into the first order and discovered that if you try to look at that Registrant's order for the event, that there is some issue with the data that causes this error:

    Click image for larger version

Name:	2018-04-17_Eric 33189.png
Views:	58
Size:	145.8 KB
ID:	39011

    I suspect this is one of the events that was improperly imported, I will look through the other cases and see if it is a similar problem in the other cases and what may be done.

    Leave a comment:


  • Eric Pitts
    started a topic Error Transactions not making it to Salesforce

    Error Transactions not making it to Salesforce

    We have had some authorized transactions not make it into Salesforce. They show in Connect as Error. We have tried to re-post them from Connect. We have also tried deleting them from Salesforce using the Maintenance feature in C&P Settings, but they don't make it over.
    Here are the order numbers:
    33189-1707251811523117425
    33189-1709122007274740237
    33189-1709261853242959787
    33189-180416162030867
    33189-180417115240447
    33189-1804171323318402776
    33189-180417134145247
Working...
X