Integration Procedure blocks, caching and long-running steps
Key Takeaway
The caller turns chaining on. Lowering limits inside an Integration Procedure has no effect until "Chainable" is checked on the Omniscript or parent Integration Procedure action that calls it.
An Integration Procedure is a server-side Omnistudio process with no end-user UI. You build it from Actions, which do the work, and Blocks, which group Actions so they run as a unit under shared rules. Blocks, caching and chaining settings let you control flow, handle errors, speed up repeat requests, and keep long-running Integration Procedures from failing on Salesforce governor limits.
Actions and Blocks
Actions perform tasks such as reading and writing Salesforce data, sending email, calling REST endpoints and running Apex. Blocks group related Actions so you can run them conditionally, repeat them for each item in a list, cache their results, or handle an error if one fails. All elements on the canvas run in order from top to bottom.
There are four block types: Cache Block, Conditional Block, Loop Block and Try-Catch Block. These blocks, along with caching and chainable settings, are Integration Procedure features that Omniscripts do not have.