Skip to main content

Hello everyone; I've found a Flow (API v56) bug where a SOQL query is concatenated incorrectly in a special case - 100% repeatable.

 

I run Get Records with filter on:

ID in {var_string_collection} and the collection is null.

You will see the error in the query concatenation (missing whitespace) before the ORDER BY statement leading to ugly crash.

 

How can I report this bug to SF?

 

***

Error Occurred: This error occurred when the flow tried to look up records: SystemModstamp, OwnerId FROM CampaignORDER BY StartDate DESC LIMIT 50001 ^ ERROR at Row:1:Column:1159 unexpected token: BY. You can look up ExceptionCode values in the SOAP API Developer Guide.

***

3 件の回答
  1. 2025年11月17日 16:20

    Just encountered the same issue myself, with the same set of conditions.  

     

    If the collection is non-null, it works fine.  

    If there is no sort specified on the Get Records component, it works fine.  

    If there is no 'IN' (list) criteria on the Get Records component, it works fine. 

     

    As soon as you combine those three criteria, it fails.  

     

     

    I've opened a case with SF to report this, as I can't find it recorded as a known issue - this is the only article or thread I can find referencing it. 

0/9000