AddTraxJobRunner

Registers the minimal services needed to run JobRunnerTrain without the full scheduler. Used on the remote receiver side — the process that actually executes trains dispatched by a scheduler via UseRemoteWorkers(). Also documents UseTraxRunEndpoint() for handling synchronous run requests from UseRemoteRun().

Signatures

public static IServiceCollection AddTraxJobRunner(
    this IServiceCollection services
)

public static RouteHandlerBuilder UseTraxJobRunner(
    this IEndpointRouteBuilder app,
    string route = "/trax/execute"
)

public static RouteHandlerBuilder UseTraxRunEndpoint(
    this IEndpointRouteBuilder app,
    string route = "/trax/run"
)

Parameters

AddTraxJobRunner

No parameters. Registers the execution pipeline services only.

UseTraxJobRunner

UseTraxRunEndpoint

Examples

Minimal Remote Executor (Queue Only)

var builder = WebApplication.CreateBuilder(args);
 
builder.Services.AddTrax(trax => trax
    .AddEffects(effects => effects
        .UsePostgres(connectionString)
    )
    .AddMediator(typeof(MyTrain).Assembly)
);
builder.Services.AddTraxJobRunner();
 
var app = builder.Build();
app.UseTraxJobRunner("/trax/execute");
app.Run();

Remote Executor (Queue + Run)

var builder = WebApplication.CreateBuilder(args);
 
builder.Services.AddTrax(trax => trax
    .AddEffects(effects => effects
        .UsePostgres(connectionString)
    )
    .AddMediator(typeof(MyTrain).Assembly)
);
builder.Services.AddTraxJobRunner();
 
var app = builder.Build();
app.UseTraxJobRunner("/trax/execute");  // queue path
app.UseTraxRunEndpoint("/trax/run");    // synchronous run path
app.Run();

> Note: UseTraxRunEndpoint() does not require AddTraxJobRunner(). It uses ITrainExecutionService which is registered by AddMediator(). Only add AddTraxJobRunner() if you also need the queue execution path.

With ASP.NET Authentication

Trax doesn't bake in any auth. The endpoint mapped by UseTraxJobRunner() is a standard ASP.NET minimal API endpoint — secure it however you normally would:

var builder = WebApplication.CreateBuilder(args);
 
builder.Services.AddTrax(trax => trax
    .AddEffects(effects => effects
        .UsePostgres(connectionString)
    )
    .AddMediator(typeof(MyTrain).Assembly)
);
builder.Services.AddTraxJobRunner();
builder.Services.AddAuthentication(/* your scheme */);
builder.Services.AddAuthorization();
 
var app = builder.Build();
app.UseAuthentication();
app.UseAuthorization();
app.UseTraxJobRunner("/trax/execute").RequireAuthorization();
app.Run();

AWS Lambda (via TraxLambdaFunction base class)

For Lambda deployments, use the Trax.Runner.Lambda package which provides a base class that handles service provider lifecycle, request routing, and cancellation:

using Amazon.Lambda.Core;
using Amazon.Lambda.Serialization.SystemTextJson;
using Trax.Runner.Lambda;
 
[assembly: LambdaSerializer(typeof(DefaultLambdaJsonSerializer))]
 
public class Function : TraxLambdaFunction
{
    protected override void ConfigureServices(IServiceCollection services, IConfiguration configuration)
    {
        var connString = configuration.GetConnectionString("TraxDatabase")!;
 
        services.AddTrax(trax => trax
            .AddEffects(effects => effects.UsePostgres(connString))
            .AddMediator(typeof(MyTrain).Assembly));
    }
}

See the TraxLambdaFunction API reference for details.

What It Registers

AddTraxJobRunner

Registers the minimum set of services to run JobRunnerTrain:

Not registered: ManifestManager, JobDispatcher, polling services, startup service, LocalWorkerService. This process only runs trains — it doesn't schedule or dispatch them.

UseTraxJobRunner

Maps a POST endpoint at the specified route that:

1. Reads a RemoteJobRequest from the request body
2. Deserializes the input (if present) using the fully-qualified type name
3. Creates a new DI scope and resolves IJobRunnerTrain
4. Calls Run(new RunJobRequest(metadataId, input))
5. Returns 200 OK with a RemoteJobResponse containing the metadata ID on success
6. On error: returns 200 OK with RemoteJobResponse.IsError = true and structured error fields (ErrorMessage, ExceptionType, StackTrace)

UseTraxRunEndpoint

Maps a POST endpoint at the specified route that handles synchronous run requests from UseRemoteRun():

1. Reads a RemoteRunRequest from the request body (contains train name and input JSON)
2. Resolves ITrainExecutionService and calls RunAsync(trainName, inputJson)
3. Serializes the train output as JSON
4. Returns 200 OK with a RemoteRunResponse containing the metadata ID, output JSON, and output type
5. On error: returns 200 OK with RemoteRunResponse.IsError = true and structured error fields (ErrorMessage, ExceptionType, FailureJunction, StackTrace). Uses in-band errors to distinguish from infrastructure failures

Shared Requirements

The remote process must:

• Reference the same train assemblies passed to AddMediator() — train types are resolved by fully-qualified name
• Connect to the same Postgres database — metadata, manifests, and state are shared across all processes
• Register the effect system — AddTrax() with UsePostgres() is required

Package

dotnet add package Trax.Scheduler

See Also

• Remote Execution — architecture overview and deployment models
• UseRemoteWorkers — scheduler-side configuration for HTTP dispatch (queue path)
• UseRemoteRun — scheduler-side configuration for remote run execution
• AddTraxWorker — standalone worker (poll-based alternative)