Process flow consisting of a chatter action "Post to Chatter" throws an error when deployed via change sets
Trailblazer Community

Known Issues · In Review

Process flow consisting of a chatter action "Post to Chatter" throws an error when deployed via change sets

Change Sets , Flow

Last updated 2020-11-04 ·Reference W-2327369 ·Reported By 66 users

In Review

Summary
Some customers have observed their process flow that was created/updated via a deployed change set throws the following error when the conditions for the flow are met:

“The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301XXXXXXXXXXX. Contact your administrator for help.”

The Process Flow in question can be as simple as the following:

Object – Opportunity
Criteria – Boolean Equals to True.
Action – Post to Chatter (Group)

This happens because we store the ID for the group in the Post To Chatter action metadata, this will be delivered to the destination org untouched and ultimately incorrectly.

So instead of looking for the API name of the group, the flow is looking for the chatter group ID which in this case is referencing the ID of the source org, eventually throwing the above error.

Repro
Source Org:

Create a Chatter Group:

1. Chatter>Group>Name

Ex: SF group

2. Create a Process that will post a message to a Chatter Group

- Setup > Create > Workflow & Approvals > Process Builder > New
- Choose the Opportunity object
- Choose "when a record is created or edited"
- Leave the Advanced checkbox uncheck
- Save

3. Define Criteria for this Action Group

- For the criteria: (same as the customer)
Checkbox Equals True
- Conditions: Choose "Any of the conditions are met (OR)"
- Leave the Advanced checkbox uncheck
- Save

4. Action

- Post to Chatter
- Select a Chatter Group
- Enter a message.
- Save

Open Opportunity record and set the checkbox (process criteria) to True. Open the Chatter Group specified on the Process
Message should be posted to Chatter Group

5. Create an Outbound Change set

- Setup>Deploy> Outbound Change Sets> Add> Add the Process created in steps 2 - 4 >Upload

Target Org:

6. Go to the Target Org and Deploy:

- Setup> Deploy> Inbound Change Sets> Deploy> Default> Save

7. Activate the Process Flow

- Setup> Create> Workflow & Approvals> Process Builder> Click on the process> Activate

8. Open an Oppty record>meet the criteria for the Process to fire and you will see an error as follows:

“The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301XXXXXXXXXXX. Contact your administrator for help.”

Workaround
- Open the flow/process and recreate the Post To Chatter action in order to pull in the new ID reference.

Reported By (66)

美穂 柴田 O Luijten Todd Bachamp Arun Kumar Ravi Prakash Jangid William Tsoi sai santosh Suddula Noelle Lafferty 芙美香 溝渕 Zoë Vokes Ritika Rawlani Arun Kumar Tim Schuitemaker Lori Gordon David Tompkins Ankur Anand Sandra Radzimska Lisa Wilbur Janell Parga (Admin) Kurt Orto Karthik Pallerla Marty Kopka Kristin Cecil (work) Maria Huemmer Chris Chomka Alex Lui Denise Hensal 憲司 仲矢 Tommy Strickland Kevin Crews 水野　賢治 Arjun Gupta Srilaxmi Somasani AMIT AGRAWAL Amy Mitchell Ryan Mott Avinash Gaikwad Scott Walker Salesforce SystemAdmin Lars Eskebæk Crystal Karanovich Jared Steiner Michael Moran Eden Brecht Jeroen Burgers Vroni Mylle Matt Norn Ben Prozinski Deepanshu Gupta Pedro Freire Madlen Kopp Selva Sundari Jim Carey Bruce Stewart John Norman Chris Uttley Rhonda Ross Lori Alario Michael Ludwig (Darmstadt) Raghavendar Madireddy Kim Headrick Rachel Burcher Uday Kumar Aladin Banwal Kenneth Patrick Chad La Fournie

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP24 AP25 AP26 AP27 AP28 CS1 CS2 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS123 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS137 CS138 CS133 CS132 CS14 CS148 CS142 CS159 CS152 CS151 CS15 CS162 CS16 CS169 CS165 CS160 CS173 CS17 CS174 CS18 CS189 CS194 CS192 CS193 CS190 CS191 CS199 CS197 CS19 CS198 CS196 CS195 CS20 CS201 CS203 CS21 CS22 CS23 CS24 CS25 CS26 CS27 CS28 CS29 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS46 CS47 CS49 CS50 CS52 CS53 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS70 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS84 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS94 CS95 CS96 CS97 CS98 CS999 CS99 EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 EU33 EU34 EU35 EU36 EU37 EU38 EU39 EU40 EU41 EU42 EU43 EU45 IND1 IND2S IND3S IND5 IND7 IND9 NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA128 NA138 NA134 NA133 NA136 NA135 NA132 NA131 NA130 NA137 NA139 NA140 NA142 NA141 NA149 NA146 NA147 NA148 NA154 NA158 NA159 NA153 NA151 NA155 NA152 NA150 NA156 NA172 NA174 NA171 NA173 NA196 NA202 NA21 NA46 NA49 NA52 NA61 NA62 NA64 NA65 NA66 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 NA80 NA81 NA82 NA83 NA84 NA85 NA86 NA87 NA88 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5 UM6 UM7

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.