Insert an Oban job in the same transaction as the Phoenix order change

A queued job belongs in the same database commit as the business change when workers depend on that change. Oban’s Multi integration keeps the job row transactional and preserves Oban-specific insertion behavior.

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 Phoenix boundary

Save this illustrative integration module as lib/shop/confirmations.ex.

defmodule Shop.Confirmations do
  alias Ecto.Multi
  alias Shop.{Repo, Order, ReceiptWorker}

  def enqueue(order) do
    Multi.new()
    |> Multi.update(:order, Order.changeset(order, %{status: "confirmed"}) |> Ecto.Changeset.optimistic_lock(:lock_version))
    |> Oban.insert(:receipt, ReceiptWorker.new(%{order_id: order.id}))
    |> Repo.transact()
  end
end

The order, inventory, or resource-lifetime scenario is adapted from Perch’s public order-service source at commit 4af67af. This Phoenix implementation is an illustrative adaptation.

Integrate with your application

Configure Oban on the same Repo and database used by the Multi. Implement ReceiptWorker as an idempotent worker and define a unique-job policy appropriate to the event identity. Authorize the order in the context before building this Multi. Job uniqueness reduces duplicate insertion but does not make external email or payment effects exactly once; the worker must preserve a stable idempotency key across retries.

Exercise the boundary and failure paths

Add regression tests for these cases in your existing Phoenix 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:

mix test test/shop/confirmations_test.exs

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:

|> Oban.insert(:receipt, ReceiptWorker.new(%{order_id: order.id}))

with:

|> Multi.run(:receipt, fn _repo, _changes -> {:ok, :not_enqueued} end)

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-phoenix-oban-atomic-job.yaml at the repository root, keeping your existing perch.yaml:

- name: confirmation-inserts-oban-job
  where: "lib/shop/confirmations.ex"
  ensure: >-
    The confirmation Multi must insert the ReceiptWorker job using Oban.insert before Repo.transaction. A placeholder success without a persisted job violates the requirement.

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

npm install -g @lakeday/perch
perch login
perch check lib/shop/confirmations.ex --rules confirmation-inserts-oban-job --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.

The rule distinguished these controls in this run. Raw Perch capture · Exact sources and mutation.

Install the rule pack and configure your agent

Download this rule pack ZIP · Download the YAML rules · Agent task. 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:

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:

curl -fL 'https://frameworkrecipes.dev/phoenix/oban-atomic-job/rule-pack.zip' -o 'perch-guide-phoenix-oban-atomic-job.zip'
unzip -n 'perch-guide-phoenix-oban-atomic-job.zip'

The installed rule is .perch/rules/perch-guide-phoenix-oban-atomic-job.yaml. Its selector matches lib/shop/confirmations.ex 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:

perch setup claude-code

Codex:

perch setup codex

Cursor:

perch setup cursor

Pi:

perch setup pi

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

Use the installed Perch skill while editing lib/shop/confirmations.ex. Preserve confirmation-inserts-oban-job. Run perch check lib/shop/confirmations.ex --rules confirmation-inserts-oban-job --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:

perch check lib/shop/confirmations.ex --rules confirmation-inserts-oban-job --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

• hexdocs.pm reference

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.