A job is recorded with its business change and started after the commit

Context

Database submission and orchestration start cannot commit as one transaction.

Decision

Commit the business records and job together, then call the start helper appropriate to the caller. The forgiving helper logs a failed start and returns the recorded job. Strict callers propagate the error; reconciliation can later fail an unstarted job.

Alternatives Considered

Starting before commit risks orphaned execution. A separate queue would add start recovery machinery. Uniform error handling would obscure the distinction between committed work and execution failure.

Consequences

Clients and operators need to distinguish a committed submission from a successful execution start.