Error "Apex CPU time limit exceeded" when creating Work Orders in Salesforce Field Service

Resolution

Step 1: Enable Debug Logging and Identify the Bottleneck

Enable a debug trace flag for your user and re-run the Work Order creation flow. Review the debug log to identify which Apex actions, decisions, or queries consume the most CPU time. Look for repeated queries in loops or inefficient SOQL statements.

Step 2: Optimize Apex Logic

If the flow calls custom Apex:

- Refactor loops to use bulk operations instead of processing records one at a time.
- Move queries outside loops; use a single query with proper filtering and store results in a variable.
- Remove unnecessary field selections; query only the fields your logic requires.
- Avoid calling external APIs synchronously; use `@future` or Queueable Apex to defer the callout to an asynchronous context.

Step 3: Simplify Flow Logic

- Reduce the number of nested decision elements; combine conditions where possible.
- Avoid loops that iterate over large record sets; use batch processing or asynchronous subflows instead.
- Remove unused formula field evaluations or move them to a separate, asynchronous flow.

Step 4: Convert to Asynchronous Processing

If the Work Order creation does not require an immediate response to the user, convert the flow to run asynchronously:

- (unverified-control) Set the flow's trigger to run asynchronously, or wrap the heavy logic in a scheduled action or subflow that runs after the initial transaction completes.
- Asynchronous transactions have a 60-second CPU time limit, providing more headroom for complex automation.

Step 5: Adjust Batch Size or Record Limits

If the flow processes multiple Work Orders in a batch:

- Reduce the number of records processed per flow execution.
- Implement pagination or chunking logic to split large batches into smaller transactions.