Announcement

Collapse

Information Needed

See more
See less

Auto-responder email created in C&P Designer not going to BCC emails

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Auto-responder email created in C&P Designer not going to BCC emails

    We just recently got help from support getting our Salesforce and C&P re-connected, so now the correct receipt goes out but it is not kicking back to the email addresses I put in under BCC in both the Email and Default tab under Autoresponder in C&P Settings. Any help would be greatly appreciated!


  • #2
    Good day @rachaeldeg

    Would you please share the Autoresponder name and the most recent order number for which bcc didn't get the responder?

    Looking forward to hearing back from you.
    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
      Great thank you!

      The Autoresponder name is Thank You single donation and the most recent order number that bcc didn't get the responder is 23823-1708031012158921001

      I don't know if this is related or helps, but we also got two error messages on Monday of this week, one from this order number: 23823-170503135204840 and this one 150408180700329. The error said, "Upsert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, npsp.TDTM_Opportunity: execution of AfterInsert

      caused by: System.DmlException: Update failed. First exception on row 0 with id 001j000000CttjeAAB; first error: CANNOT_EXECUTE_FLOW_TRIGGER, The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301j00000004rBu. Flow error messages: <b>An unhandled fault has occurred in this flow</b><br>An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. Contact your administrator for help.: []"

      Thank you!

      Comment


      • #4
        Good day @rachaeldeg

        We reviewed and found NO reason to NOT to fire the responder for bcc since I see the Autoresponder logs for the respective order#23823-1708031012158921001. I see that there are 3 emails listed under bcc, are those all didn't receive the responder? I am wondering if the email are being blocked or ending up in a spam folder. Please check email/spam/junk/ folder for the email.

        Regarding the order#23823-170503135204840 the error itself represent that it has been caused by trigger on opportunity object which also the reason the Autoresponder didn't fire. Please review the trigger and repost the data.
        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
          Hello!

          That's right NONE of the emails under BCC received the responder. I just double checked my spam folder and it isn't there. I will look into things on the Outlook side.

          In response to the error, I reviewed it in connect last week and posted it to SF again but got the same error. I attached a screen shot of the email.

          Thank you!

          Comment


          • #6
            Good day @rachaeldeg

            We reviewed your instance and found that the reason for getting the above error is because of the following workflow:

            Click image for larger version

Name:	WorkFlow.jpg
Views:	45
Size:	114.8 KB
ID:	34234

            Please deactivate the above flow and try to repost the data.

            Please check and 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


            • #7
              Ok great! We had an outside consultant set up those workflows so I'm afraid that will mess something up if I deactivate. Do you think that will be a problem? Also I tested the BCC issue stated above by adding my gmail address to the BCC list and it still didn't kick back. So its not an Outlook issue. Do you think you could investigate further?

              Thank you so much for all your help! We so appreciate it.

              Comment


              • #8
                Good day @rachaeldeg

                One of our developers reviewed your instance and concluded that above mentioned workflow is causing the issue. You may deactivate and repost the data and test it.

                Would you please share the order number of the transaction which you are referring to?
                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
                😀
                🥰
                🤢
                😎
                😡
                👍
                👎