This other community post might help you:
We are setting AsyncProcessingDisabled before loading. In this case we don’t want to have the fields automatically refresh due to the data load being large and backing up the queues while records are added. We know which two types have stored calcs that reference the data. They have a sum over a collection (and the collection keeps changing as new records are loaded) so it causes a backup when it is more efficient (and will actually complete) if we refresh at the very end once.
If you disable AsycProcessing, why dont you just run refreshCalcs after your dataload?
Given that you have a relatively complex workflow to automate, you may want to checkout the Workflow type. This will allow you to orchestrate multi-step long-running actions.
Disable AsyncProcessing -> Load Data -> Refresh Calc Fields -> Enable AsyncProcessing
Specifically for the “refreshCalcFields” step, you may want checkout the method
So that makes sense, except we don’t know exactly when LoadData will occur as the file will be posted from an internal system to the Azure blob storage. So in this case, would the “load data” step be our cron jobs that detects and processes the file? So each time it checks (say once every 30 minutes), it would run that workflow, and skip refresh calc fields if nothing got loaded?
Thanks for the info
Yes i think you could orchestrate it that way.