*Collection Processors for Flow* - _(Extract Strings From Collection [USF Collection Processor])_ - Action name not found: null

[RikusFischer]

Steps to reproduce

Steps to reproduce the behavior:

1. Create a screen flow that uses the Extract Strings From Collection [USF Collection Processor]
2. Pass record collection into component and set field to extract
3. Set allowEmptyCollection to TRUE and dedupeValues to TRUE
4. Run the Flow
5. On the first run this error occurs: "Action name not found: null"
6. Running the Flow the second time it works as expected

Screenshots

[ericrsmith35]

I've tried to recreate this and I am not seeing any errors.

[MlleBaeten]

We are also seeing this error with two actions within the CollectionActionsL package:

• Get First
• Extract Strings From Collection We see the error intermittently, but then when we run the flow again to recreate the issue, the flow runs as expected. Can't find any cause for this issue. Running latest version of CollectionActionsL: 3.1.1.

[RikusFischer]

I was able to fix it by recompiling the Apex Classes. I realised this only happened in our Staging and UAT environments and not in the dev environment.

[jeremywatso]

We are also experiencing the exact same issue, intermittently, in our of our production orgs with both:

• Find Records in Collection
• Extract Strings From Collection

Also running latest version of collectionActions 3.2.0

[ericrsmith35]

@alexed1 Do you know why this could be happening?

[BaileyAnn]

my org started see this error today for Dedupe_Record_Collection (FlowActionCall).

You’ve received this email because an error occurred while your "SA-SCR-SF-Sales Agreement SPA .csv BOM Import" flow was running.
Error element Dedupe_Record_Collection (FlowActionCall).
Action name not found: null 

[jeremywatso]

For the record, I can attest that recompiling Apex Classes worked like Rikus said. Also I tested this once I had consistently this error with a user, I simply opened the Apex class that was failing, refreshed my page with the screenflow that was generating this action: null issue, and it worked. However even if you do this once, it reappeared the next day and had to do it again.

In the end I decided to remove the actions from my flows and build them manually in flow instead...

[samphif]

I'm also experiencing this as well. ive decided to hold on upgrades from 3.1.1 as it seemed to get way worse. thought we were completely clear but the issue rearose after a month

[ericrsmith35]

I have case open with Salesforce for this issue.

On Thu, Jan 25, 2024 at 2:24 PM Sam Phifer @.***> wrote:

I'm also experiencing this as well. ive decided to hold on upgrades from 3.1.1 as it seemed to get way worse. thought we were completely clear but the issue rearose after a month

— Reply to this email directly, view it on GitHub https://github.com/alexed1/LightningFlowComponents/issues/1437#issuecomment-1910840717, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4UHX56XF6A62BSF3MSWH3YQKWPDAVCNFSM6AAAAAA2STHZMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJQHA2DANZRG4 . You are receiving this because you commented.Message ID: @.***>

[ericrsmith35]

Salesforce has found and patched this bug in Spring '24 orgs.

[samphif]

Awesome great news.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Eric Smith @.> Sent: Wednesday, February 7, 2024 3:58:59 PM To: alexed1/LightningFlowComponents @.> Cc: Sam Phifer @.>; Comment @.> Subject: Re: [alexed1/LightningFlowComponents] Collection Processors for Flow - (Extract Strings From Collection [USF Collection Processor]) - Action name not found: null (Issue #1437)

Salesforce has found and patched this bug in Spring '24 orgs.

— Reply to this email directly, view it on GitHubhttps://github.com/alexed1/LightningFlowComponents/issues/1437#issuecomment-1932879081, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMQAAD2UC5G2OPUOWBB56O3YSPTJHAVCNFSM6AAAAAA2STHZMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZSHA3TSMBYGE. You are receiving this because you commented.Message ID: @.***>

[dougepsotic]

Salesforce has found and patched this bug in Spring '24 orgs.

@ericrsmith35 I am still seeing the "Action name not found: null" error on ConvertCSVToStringCollection. So not sure this patched solved the issue.