Announcement

Collapse

Information Needed

See more
See less

Connect/Event transactions not coming over to Salesforce

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

  • Connect/Event transactions not coming over to Salesforce

    It appears that online gift and event registration transactions are no longer posting to salesforce. This started happening about 6:30 This morning. At last count, we had 230+ transactions that haven't posted. Here's a copy of the error message we've been getting:
    Error element myRule_1_A1 (FlowRecordUpdate).
    The flow tried to update these records: null. This error occurred: LIMIT_EXCEEDED: System.LimitException: Apex CPU time limit exceeded. You can look up ExceptionCode values in the SOAP API Developer Guide.---The flow tried to update these records: null. This error occurred: LIMIT_EXCEEDED: System.LimitException: Apex CPU time limit exceeded. You can look up ExceptionCode values in the SOAP API Developer Guide.


    Flow Details
    Flow API Name: OPP_Update_Location_Purpose_Project_Code
    Type: Record Change Process
    Version: 2
    Status: Active
    Org: MADD (00DF00000006xCG)
    Flow Interview Details
    Interview Label: OPP_Update_Location_Purpose_Project_Code-2_InterviewLabel
    Current User: Chris Robinson (005F00000045u45)
    Start time: 7/30/2019 2:32 PM
    Duration: 0 seconds
    How the Interview Started
    Chris Robinson (005F00000045u45) started the flow interview.
    Some of this flow's variables were set when the interview started.
    myVariable_old = null
    myVariable_current = Opportunity (0062I000012kS78QAE)
    ASSIGNMENT: myVariable_waitStartTimeAssignment
    {!myVariable_waitStartTimeVariable} Equals {!$Flow.CurrentDateTime}
    Result
    {!myVariable_waitStartTimeVariable} = "7/30/2019 2:32 PM"
    DECISION: myDecision
    Outcome executed: myRule_1
    Outcome conditions:
    1. {!myVariable_current.CampaignId} (7012I0000010E3KQAU) Is null false
    2. {!myVariable_current.Purpose_Code_if_different_fro m_Campaign__c} (null) Is null true
    Logic: All conditions must be true (AND)
    UPDATE RECORDS: myRule_1_A1
    Find all Opportunity records where:
    Id Equals {!myVariable_current.Id} (0062I000012kS78QAE)
    Update the recordsí field values.
    Purpose_Code__c = {!myVariable_current.Campaign.Purpose_Code__c} (null)
    Result
    Failed to update records that meet the filter criteria.


    Error Occurred: The flow tried to update these records: null. This error occurred: LIMIT_EXCEEDED: System.LimitException: Apex CPU time limit exceeded. You can look up ExceptionCode values in the SOAP API Developer Guide.---The flow tried to update these records: null. This error occurred: LIMIT_EXCEEDED: System.LimitException: Apex CPU time limit exceeded. You can look up ExceptionCode values in the SOAP API Developer Guide.




    Flow Details
    Flow API Name: OPP_Update_Location_Purpose_Project_Code
    Type: Record Change Process
    Version: 2
    Status: Active
    Org: MADD (00DF00000006xCG)
    Flow Interview Details
    Interview Label: OPP_Update_Location_Purpose_Project_Code-2_InterviewLabel
    Current User: Chris Robinson (005F00000045u45)
    Start time: 7/30/2019 2:32 PM
    Duration: 0 seconds
    How the Interview Started
    Chris Robinson (005F00000045u45) started the flow interview.
    Some of this flow's variables were set when the interview started.
    myVariable_old = null
    myVariable_current = Opportunity (0062I000012kS79QAE)
    ASSIGNMENT: myVariable_waitStartTimeAssignment
    {!myVariable_waitStartTimeVariable} Equals {!$Flow.CurrentDateTime}
    Result
    {!myVariable_waitStartTimeVariable} = "7/30/2019 2:32 PM"
    DECISION: myDecision
    Outcome executed: myRule_1
    Outcome conditions:
    1. {!myVariable_current.CampaignId} (7012I0000010E3KQAU) Is null false
    2. {!myVariable_current.Purpose_Code_if_different_fro m_Campaign__c} (null) Is null true
    Logic: All conditions must be true (AND)
    UPDATE RECORDS: myRule_1_A1
    Find all Opportunity records where:
    Id Equals {!myVariable_current.Id} (0062I000012kS79QAE)
    Update the recordsí field values.
    Purpose_Code__c = {!myVariable_current.Campaign.Purpose_Code__c} (null)
    Result
    Failed to update records that meet the filter criteria.


    Error Occurred: The flow tried to update these records: null. This error occurred: LIMIT_EXCEEDED: System.LimitException: Apex CPU time limit exceeded. You can look up ExceptionCode values in the SOAP API Developer Guide.---The flow tried to update these records: null. This error occurred: LIMIT_EXCEEDED: System.LimitException: Apex CPU time limit exceeded. You can look up ExceptionCode values in the SOAP API Developer Guide.




    Salesforce Error ID: 1616624272-35614 (-1933702491)

  • #2
    Good day CRobi24

    We have re-posted the transactions from 7/29 and 7/30 to your instance successfully. Given these transactions were recent we enabled the Autoresponder posts so the patrons receive the auto-responder.

    In reviewing the errors we have noticed you also have similar Salesforce CPU errors dating back to 7/18, 7/17, 7/16, 7/15, 7/11 and a few dating from January. A total of 45 transactions have not posted to your Salesforce Since January 1, 2019. We can post those transactions to your instance and set the Autoresponder to OFF so the patrons do not receive the post - to avoid confusion.

    We did not want to post them without checking with you. Of course, you could easily post them yourself through Connect but in case you want us to bulk-post all of them just let us know.
    Regards,
    Click & Pledge Support Department

    On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

    Join us @ the educational webinars: https://clickandpledge.com/webinars/
    Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
    Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

    Comment


    • #3
      Thank you! Yes, please post those other transactions with the Autoresponder set to "OFF". We think we might know what happened. It appears that a couple of Salesforce Debugger logs were going, which was using up the CPU. This likely contributed to Salesforce timeout errors. Thank you very much for your help with this

      Comment


      • #4
        CRobi24

        As requested we are posting ALL 2019 transactions to your Salesforce instance with Autoresponder flag set to "Not Send".

        We will update this post once the sync has completed.
        Regards,
        Click & Pledge Support Department

        On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

        Join us @ the educational webinars: https://clickandpledge.com/webinars/
        Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
        Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

        Comment


        • #5
          CRobi24

          The re-post of all 2019 transactions that had error'd due to CPU issue is now complete.

          Please check your instance & let us know if we can be of any further assistance.
          Regards,
          Click & Pledge Support Department

          On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

          Join us @ the educational webinars: https://clickandpledge.com/webinars/
          Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
          Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

          Comment

          Working...
          X