unusual behavior - temp contacts not creating opportunities

[[email protected]]

Just adding info in case this is helpful - this mainly seems to be happening when the name and email in the C&P data are not an exact match to an existing contact, but it also happens with some temp contacts for which there is no existing contact. In the case of the existing contacts, is it possible that my duplicate rules are part of the issue? If so, if you could check whether I have those set correctly, that would be amazing.

I'm pasting below a new errors that I've received, as well, in case this is informative:

Visualforce Page: /apex/cnp_paas_evt__EventTemporaryContact

caused by: System.DmlException: Update failed. First exception on row 0 with id a1G5c00000CtX3tEAF; first error: INVALID_ID_FIELD, invalid record id: []

Class.CnP_PaaS_EVT.EventTemparyContact.SaveItem: line 304, column 1

[CnP.Support.AM]

Good day @[email protected]

I see that the two order numbers you shared have been processed successfully. Would you please share the new temp contact order numbers which have the error so that we can review it further?

[[email protected]]

Thanks - you could look at these order numbers:

28969-2210101646562778586

28969-2209161713273617788

I'm sure there will be more by the end of the day today, if you need more to look at. Much appreciated!

[[email protected]]

I've created a View for C&P Data with errors, so you can also check this for more:

https://npsafoundation.lightning.force.com/lightning/o/CnP_PaaS__CnPData__c/list?filterName=00B5c000007nRBMEA2

[CnP.Support.AM]

Good day @[email protected]

We have fixed the issue in your instance and processed the errored order numbers.

The issue was, in the presence of NPSP we are having the Async process from Temp which is due to a number of factors to avoid CPU Time and Execution Time exceptions. For example, custom fields in Contact/Account/Opportunity are more than 100 fields in each object, the number of custom mapping and workflow rules, and the number of Opportunity triggers...etc.

Flow rule has a number of parameters to pass the information, in your case, one of the values of the parameter is missing for the required field when it is trying to create one of the records in the object. We tried to debug it but were unable to find the object in the logs.

However, we have disabled the process in Async mode in your instance to avoid the above issue.

Please check and let us know if we can be of any further assistance.

[[email protected]]

Hi! I was so relieved that this got fixed, and then I forgot to post and let you know that all is well. I appreciate it very much. Thank you.