Aglet

Verify scheduled runs that finish before and after the interval

Verification must prove what happens when one occurrence is still active at the next due time. Run a short control and a deliberately spanning case with the same schedule. Compare both run IDs, guard state, output ownership, and terminal records after any queued work settles.

Check whether the outcome improved

  1. Verify the short control

    Let the first occurrence finish before the next due event. Confirm the next occurrence is created once, claims normally, and writes the expected output. Record lock release or policy state so the spanning case has a real baseline.

  2. Verify a spanning occurrence

    Pause the first run across the next due time and inspect the second run’s documented state. Confirm it is skipped, queued, locked, or admitted intentionally. Reconcile shared outputs and ensure a visible overlap does not imply two successful writes when only one is allowed.

  3. Verify eventual settlement

    Release the first run and let any queued or concurrent second occurrence settle. Check run IDs, terminal states, output versions, and downstream reads. Exercise a lease or worker interruption only if it is part of the overlap contract, keeping it labeled as a separate case.

What to carry forward

Accept when short and spanning runs follow the stated overlap policy, with output ownership and terminal states reconciled. Keep intentional concurrency visible. Reopen verification if a lock expires without an owner decision, a queued run is lost, or two occurrences can commit the same effect unexpectedly.

Technical background: Rails guides.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow