# Dispatch Laravel order jobs only after the transaction commits

A worker can pick up a queued job before the order transaction commits. Deferring dispatch prevents that race and discards dispatch when the transaction rolls back. It still leaves a durability question between committing state and successfully enqueuing a job.

Save this requirement in Perch and check it after each agent edit. The rule gives your agent a named check to run, a finding to repair, and the same command to recheck.

## Implement the Laravel boundary

Save this illustrative integration module as `app/Actions/ConfirmOrder.php`.

```php
<?php
namespace App\Actions;
use App\Jobs\SendOrderConfirmation;
use App\Models\Order;
use Illuminate\Support\Facades\DB;

class ConfirmOrder {
    public function handle(int $tenantId, int $orderId): void {
        DB::transaction(function () use ($tenantId, $orderId) {
            $order = Order::where('tenant_id', $tenantId)
                ->whereKey($orderId)->lockForUpdate()->firstOrFail();
            if ($order->status !== 'pending') throw new \RuntimeException('Not pending');
            $order->status = 'confirmed';
            $order->saveOrFail();
            SendOrderConfirmation::dispatch($order->id)->afterCommit();
        });
    }
}
```

The order, inventory, or resource-lifetime scenario is adapted from Perch’s public [order-service source at commit 4af67af](https://github.com/lakeday-org/perch/blob/4af67af46d76ac99398d61c7ad0a45441760d4dc/test/fixtures/order-service/checkout.py). This Laravel implementation is an illustrative adaptation.

## Integrate with your application

Configure a real asynchronous queue connection and an Order model. Resolve tenantId from the authenticated user. Use an outbox if losing a notification during process failure is unacceptable. Queue fakes are useful for assertions but should not be the only test of commit timing; run an integration case with the real queue driver.



## Exercise the boundary and failure paths

| Scenario | Expected outcome |
| --- | --- |
| Successful confirmation | Job becomes eligible after commit |
| Exception inside transaction | No confirmation job dispatched |
| Worker is fast | Cannot read the uncommitted new state |
| Queue unavailable after commit | Record failure and retry delivery through a durable design |

Add regression tests for these cases in your existing Laravel test project. Use separate connections or deliberately reordered completion where the case involves concurrency; a sequential happy-path test does not exercise that failure. Run the test command after creating the matching test file or suite:

```sh
php artisan test --filter=ConfirmOrderTest
```

The scenarios above specify tests to implement. A completed Perch source check below is separate from running these application integration tests.

## Introduce the specific agent regression

In a throwaway copy, replace this source span:

```php
->afterCommit()
```

with:

```php
// Remove the source span shown above.
```

Run the relevant negative test and the Perch command on that broken copy. Restore the corrected source before committing the application. The supplied mutation reproduces the exact regression for the rule check.

## Preserve the requirement as a Perch rule

Save this in `.perch/rules/perch-guide-laravel-after-commit-job.yaml` at the repository root, keeping your existing `perch.yaml`:

```yaml
- name: job-after-commit
  where: "app/Actions/ConfirmOrder.php"
  ensure: >-
    The order-confirmation job is explicitly deferred until the surrounding database transaction commits: SendOrderConfirmation::dispatch($order->id) is chained with ->afterCommit(). Plain dispatch inside the transaction does not meet this requirement.
```

Install and authenticate the CLI once, then check the current working file:

```sh
npm install -g @lakeday/perch
perch login
perch check app/Actions/ConfirmOrder.php --rules job-after-commit --json
```

Use Node 22 or newer. The framework can use another language; Perch’s CLI remains a Node command. A gated finding exits 3. Exits 1 or 2 mean the check did not complete and must be reported as a blocker.

## Inspect the captured rule check

On 2026-10-14, Perch using jev-latest checked the exact fixed and broken source provided here. The capture records SHA-256 hashes of both sources and the requirement.

| Source control | Exit | Outcome |
| --- | --- | --- |
| Broken | 3 | Rule finding |
| Corrected | 0 | No rule finding |

The rule distinguished these controls in this run. [Raw Perch capture](/after-commit-job/capture.json) · [Exact sources and mutation](/after-commit-job/source.json).

## Install the rule pack and configure your agent

[Download this rule pack ZIP](/after-commit-job/rule-pack.zip) · [Download the YAML rules](/after-commit-job/rules.yaml) · [Agent task](/after-commit-job/agent-task.txt). The pack contains the rule, its example paths and the repair/recheck instructions. Review the `where` selector before using it in an existing project. Keep your root `perch.yaml`; install this rule as a separate file under `.perch/rules/`.

1. Install Perch using Node 22 or newer and sign in once:

```sh
npm install -g @lakeday/perch
perch login
```

2. Download the pack, inspect it, and extract it from your repository root. The extraction preserves any existing files:

```sh
curl -fL 'https://reporules.fyi/laravel/after-commit-job/rule-pack.zip' -o 'perch-guide-laravel-after-commit-job.zip'
unzip -n 'perch-guide-laravel-after-commit-job.zip'
```

The installed rule is `.perch/rules/perch-guide-laravel-after-commit-job.yaml`. Its selector matches `app/Actions/ConfirmOrder.php` in this example; adapt the selector to your application file before checking an existing project.

3. Configure the coding agent you use. Run one of these commands:

Claude Code:

```sh
perch setup claude-code
```

Codex:

```sh
perch setup codex
```

Cursor:

```sh
perch setup cursor
```

Pi:

```sh
perch setup pi
```

4. Ask the agent to edit the implementation and check the saved requirement:

> Use the installed Perch skill while editing app/Actions/ConfirmOrder.php. Preserve job-after-commit. Run perch check app/Actions/ConfirmOrder.php --rules job-after-commit --json after the edit. Read each finding and the affected code, fix the implementation, and run the identical check again after the fix. Keep the rule and regression tests intact. Run the application's relevant regression tests and report the commands and actual results. Exit 3 means a rule finding; exit 1 or 2 means the check did not complete. Report an unavailable or incomplete check as blocked. Do not claim the application tests ran if only the Perch check ran.

5. After repairing a finding, run the same check again and inspect the result:

```sh
perch check app/Actions/ConfirmOrder.php --rules job-after-commit --json
```

Commit the downloaded rule and the installed agent configuration with your application. The rule file adds no guarantee of correctness; keep the regression tests from this guide.

With the base reference fetched, use `perch scan --since origin/main --filter type=lint` in CI.

## Framework references and verification scope

- [laravel.com reference](https://laravel.com/framework/docs/13.x/queues#jobs-and-database-transactions)

The dated capture records the source check shown above. Implement the adapters, schema and regression tests described in this guide in your application. Unchanged requests reuse cached answers; fresh model judgments can vary. Model analysis sends relevant source to the configured service.