These entries are Future instance methods. You call them on a value such as one returned from runAsync. After the previous stage completes, the callback you pass runs on the completing thread (the thread that completes the prior stage), not on the separate async executor used by Async method names.

Synchronous stages add less scheduling overhead and keep ordering tight with the completion of the prior step. They are a good default for small, fast work (mapping a number, building a struct, short logging). If the follow-up might block or run for a long time, prefer the matching Asynchronous functions topic and the Async methods so the completing thread returns to the pool quickly.

ColdFusion still supports runAsync and fluent then and error on futures for existing applications. The methods listed here align with CompletableFuture naming and behavior: they compose pipelines and error paths in fine-grained steps alongside those entry points.

Each method name below links to a dedicated reference topic with syntax, parameters, and examples. The same topics appear under this map in the groups Chaining — sync (completing thread) and Completion and errors — sync.

Single-result chaining, dual-future merge, and either-first (race) patterns when follow-ups run synchronously after completion.

Observe completion, map success and failure into one value, or recover from errors while callbacks run on the completing thread.

Short sync chain after runAsync: map twice on the completing thread, then read the result.