Integration Procedures15% of the exam

Chainable and queueable chainable Integration Procedures

How to split a long-running Integration Procedure into several transactions: enable Chainable or Queueable on the calling action, set Chainable and Queueable Chainable limits and Chainable Actual Time, use Chain On Step and Disable Chaining, test with Preview options, and handle vlcStatus InProgress responses in a custom caller.

Official exam objective
Implement chainable integration procedures to split long running processes into multiple transactions.

~8 min read · 6 practice questions ·

What the exam expects

  • Enable chaining from the caller (Omniscript action, parent procedure action, REST option, Preview option) and set the thresholds in the procedure's Procedure Configuration.
  • Choose the Chainable or Queueable Chainable setting that matches the limit at risk, including Chainable Actual Time for the Concurrent Request Limit.
  • Explain when chaining actually happens, what Chain On Step and Disable Chaining change, and why chaining can cost performance.
  • Handle intermediate vlcStatus InProgress responses when a custom Lightning web component calls a chainable procedure.
  • Recognise the documented conflict about calling chainable procedures from Apex.

Key terms: chainable (a procedure allowed to continue in a new transaction when it nears a limit), queueable chainable (chainable steps that start a queueable job running as an Async Apex Job), Chain On Step (a step that gets its own transaction when a limit is reached), Chainable Actual Time (seconds a run can take before chaining), vlcIPData (the intermediate-response key a custom caller sends back).

Key facts

Default transaction
Detail
All actions run in one transaction
Where chaining is enabled
Detail
On the calling Omniscript or parent procedure action
Blank limit
Detail
Disables that check; exceeding the Salesforce limit fails the run
Chainable CPU / Heap
Detail
10,000 ms / 6 MB default maximums
Chainable Actual Time
Detail
Seconds before chaining (Concurrent Request Limit); no default
Queueable CPU / Heap / Queries
Detail
60,000 ms / 12 MB / 200
Override rule
Detail
Queueable Chainable beats Chainable when both are set
Dev Edition / Trial stack depth
Detail
5, including the parent job
Chain On Step
Detail
Optional; Help documents it for a Data Mapper Post before an HTTP action
Disable Chaining
Detail
Turns off the child's Chainable settings only; unchecked by default
LWC caller
Detail
Re-invoke while vlcIPData exists and vlcStatus is InProgress
Sources for this section (2)
  • Why can a chainable procedure still run in a single transaction?
  • When does leaving a Chainable limit blank cause a failure?
  • Which options enable chaining when testing on the Preview tab?
  • When does a custom Lightning web component need extra code to handle chaining?

The questions are free to read. Answers with their sources and self-grading are included with the pack.

Keep reading with the Omnistudio Developer pack

  • Core concepts
  • Exam traps
  • Worked scenario

The pack includes:

  • All 46 lessons of the Omnistudio Developer guide, with reading progress
  • Interactive decision walks and step-by-step sequence steppers
  • Inline practice questions and one-click topic practice (6 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Unlimited timed practice exams

Practice for the Omnistudio Developer exam