WJb Docs - Reference

NextResult

Represents a workflow transition to additional work.

NextResult indicates that execution should continue after the current action completes.

Unlike CompleteResult, which ends a workflow, NextResult creates one or more follow-up operations.

Purpose

Use NextResult when a workflow must continue.

Action
 ↓
NextResult
 ↓
Next Job

Typical examples:

Validate
 ↓
Import
Import
 ↓
Notify
Generate Report
 ↓
Send Email

Execution Flow

Job
 ↓
Action
 ↓
NextResult
 ↓
JobCommand
 ↓
Additional Jobs

The runtime translates the result into commands that enqueue the next work items.

Typical Usage

Most applications create next results through the Results helper.

return Results.Next(...);

This makes the workflow transition explicit and easy to read.

Workflow Chaining

NextResult is the foundation of workflow composition.

Step A
   ↓
Step B
   ↓
Step C

Each step completes independently and explicitly determines what should run next.

Fan-Out Workflows

A result may produce multiple follow-up operations.

Import File
      ↓
 ┌────┼────┐
 ↓    ↓    ↓
A    B    C

This allows larger workloads to be split into smaller units.

Relationship to CompleteResult

CompleteResult ends execution.

CompleteResult
      ↓
    Finish

NextResult continues execution.

NextResult
     ↓
 Next Job

Best Practices

Keep Transitions Explicit

A reader should be able to understand workflow progression by reading action results.

Prefer Small Workflow Steps

Prefer multiple focused actions:

Validate
Import
Notify

instead of one large action containing all business logic.

Use Results Helper Methods

Prefer:

Results.Next(...)

over direct construction whenever possible.

Relationship to JobCommand

NextResult describes intent.

JobCommand represents the executable instruction generated from that intent.

NextResult
      ↓
JobCommand
      ↓
Next Job

Related Types

• IActionResult
• Results
• CompleteResult
• JobCommand
• JobCommands

See Also

• Results
• CompleteResult
• JobCommand
• JobCommands