Feed

Hello @Tony Chilvers, 

You are receiving the error message "Object 500Pxxxxxxxxxxxxxxxx is currently in a merge operation, therefore a trigger can not update it," which indicates that the record is currently under a merge operation when the flow attempts to update. 

Now, as this flow works in the sandbox, it fails intermittently in production because of concurrent operations on the Case. 

To avoid trying to update the Case while it's still being processed, move the update to an asynchronous path using the Scheduled Paths feature: 

1. In your Record-Triggered Flow, click + after Start and choose Scheduled Path 

2. Set a delay: e.g., 0 Minutes After the Record is created 

3. Add the Update Records logic under this Scheduled Path 

I hope this helps to resolve your issue. 

Thanks & Regards 

Amit Kumar

Hi @Renato Mattos

. 

Could you find a solution for this? I'm facing the same problem. 

Thank you.

Your image shows that is version 1. Try creating a new version of the topic. Then save the version (without changes). Then try adding an action

Hi @Sujeet Kumar

- Did you configure the custom prompt suggesting the agent to use specific fields? Like as you are fetching using SDR email prompt template, you will have the object selected and you need to mention the fields which it should refer based on the object inside the prompt template. Kindly confirm whether that's explicitly mentioned. 

Thanks

Hello @Sham K

Use Standard Objects when possible-ensure better compatibility with Customer 360 Data Model. 

Select Only Required Field-avoid unnecessary data ingestion and improve performance. 

Enable Changeata Capture for real-time updates from Salesforce. 

Define Identify Fields Early-Helps in future Identify Resolution setup. 

Avoid Custom Lookup Loops-can create mapping issues or errors. 

Verify Object Relationships-ensure related objects are correctly mapped. 

Plan Data Limits-keep within ingestion limits to prevent throttling. 

Run Initial Sync in Off-peak Hours-minimizes impact on org performance. 

Use Descriptive Names-helps the downstream team during data activation. 

Hi @Kyle Daimler Santos Tacorda

, 

Kindly follow below steps - 

Create a new action 

You will have an option to select API 

Reference Action Category - external services 

Reference Action - the external service which is configured 

Thanks

Hi @Harshini Kadambala

, 

Kindlys hare more details on challenge. 

thanks

Hi @Jatinder Singh

, 

Points to note- 

Developer org which you refer should be with agentforce and data cloud. In legacy developer orgs the template triggered prompt flow won't be there. Kindly confirm this. 

Dev org link -

Thanks

Hi @Rahul Shah

, 

This can be done using Apex sharing (using access level methods). 

Salesforce will attempt to reinitiate same sharing access which was granted previously. Note : If there is a change which happened in sharing rules in between deletion and undeletion the access level won't be mapped. 

This is a generic feature  present. This should work here as well. 

Ref -

This article refers recalculation of rules in general. 

Thanks