Functions Apex Callbacks Fail Under High Load
Last updated 2022-03-15 ·Reference W-9999349 ·Reported By 0 users
Some customers may experience that asynchronous function invocations never receive an Apex callback when a function is invoked rapidly in a burst. This also means that the final status (error or success) of the FunctionInvocationRequest object is never updated.
Function callbacks and updates to the FunctionInvocationRequest object are delivered through the API of the invoking org. Under certain high load conditions, some of the callbacks could fail with HTTP STATUS 50x errors
Deploy a Salesforce Function and deploy Apex code to invoke it asynchronously
Setup function to at least execute for 10 seconds
Invoke the async function at > 50 requests per second
Observe that the org never receives the callback, even though the function invocation is completed successfully. Review functions logs for the presence of ASYNC_CALLBACK_ERROR
For burst workloads with time consuming functions, use sync invoke instead
Reported By (0)
Is it Fixed?
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.