Skip to main content

Has anyone had success using any of the database async methods with the SQL adapter? I'm trying with Snowflake and while database.updateImmedate() works without issue, database.updateAsync() returns the dreaded: 

FATAL_ERROR Internal Salesforce.com Error

I've tried every combination per the docs of updateAsync with a single record or a list of records, with/without access level (tried user and system levels), with/without callback class. 

 

Would love to hear anyone else's experience with this. Thanks! 

1 Antwort
  1. 23. Apr. 2024, 13:05

    Always grateful to have you help us kick the tires, Jonathan!

     

    We’ll have to look at this and figure out what we can do. The underlying problem is that some high-scale vendors have both synchronous and asynchronous processing options “natively,” but some don’t. Snowflake offers both, but all requests in Athena are asynchronous. (I believe the thinking there is that any given query they may need to walk over an enormous data set and return results minutes later…but that is problematic for use cases like the Lightning UI.)

     

    Right now, we’re just sidestepping this and delivering on a simpler happy path whereby smaller queries that can reliably work synchronously run right in line with the rest of your processing. I won’t promise Salesforce Connect will exhibit client behavior you’d consider ideal for every workload, especially with larger queries that would take a minute or more to return that need to be processed asynchronously. We will make trade-offs to prioritize many, smaller queries working well.

     

    That said, it would help to hear more about the shape of the async processing you need to do. How many records are you moving around? What are you really trying to accomplish? Feel free to send that as a separate thread if you don’t want to post it here.

0/9000