workflow
Core package for defining and running durable workflows and activities. Supports long-running persistent workflows, retries, queues, parallel execution, workflow monitoring, dedicated storage connections, and orchestration for microservices, data pipelines, sagas, agentic workflows, and other complex business processes.
Runssource: GitHubhomepagePHPMITcommit 210682a4c405
PHP, MIT licensed. The project labels itself: background jobs, bpm, bpmn, durable execution, durable functions, durable workflow, jobs and laravel.
workflow runs. An Argusic agent installed it in 45 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
composer install completes with no errors; composer unit runs 2098 tests with 15727 assertions, 3 cosmetic failures in ProjectionPrefetchTest due to PostgreSQL 16 trailing-zero timestamp format, no errors, 3 skipped, 15 PHPUnit notices. Static analysis PHPStan requires --memory-limit=-1 due to container memory constraints.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 93.5 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- PostgreSQL and Redis not available as services5 minutes
- PHP and Composer not pre-installed in container3 minutes
- Unit tests failed (531 errors) before infrastructure was available due to missing DB/Redis2 minutes
- 3 ProjectionPrefetchTest failures due to PostgreSQL 16 trailing-zero timestamp format difference (.450480 vs .45048)
- Install time
- 45 minutes
- Cold machine to finish
- 43 minutes
- Errors hit and fixed
- 4 hit, 3 fixed with no human help
- How the result was proved
- composer unit (./vendor/bin/phpunit --testsuite unit) exited 0, 2098 tests, 15727 assertions, 3 failures (all same cosmetic timestamp precision mismatch in ProjectionPrefetchTest), 15 notices, 3 skipped
- Model tokens used
- 276,658
- Exact commit tested
- 210682a4c405
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
'workflow_instance_id' => 'prefetch',
'workflow_run_id' => '01m4g5d3vx9dk0g54kpvf81tf8',
],
/work/repo/tests/Unit/V2/ProjectionPrefetchTest.php:119
FAILURES!
Tests: 2098, Assertions: 15727, Failures: 3, PHPUnit Notices: 15, Skipped: 3.
The 3 failures are identical — PostgreSQL 16 drops trailing zeros from microsecond timestamps (`.45…
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 45, "e…
tokens used
276,658
The 3 failures are identical — PostgreSQL 16 drops trailing zeros from microsecond timestamps (`.45…
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 45, "e…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 45 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Hit 4 errors during setup, 1 of which were not solved.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.20 | |
| Argusic Runner | 1/3 | Runs | 95.00 | 0.27 |
Topics (from GitHub)
background-jobsbpmbpmndurable-executiondurable-functionsdurable-workflowjobslaravelmicroservicesorchestrationphpqueueingsaga-patternworkflowworkflow-automationworkflow-engineworkflows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/workflow)Questions
- Does workflow run?
- Yes. workflow runs. Argusic installed and launched it on a clean machine in 45 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test workflow?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 210682a4c405. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test workflow?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does workflow take to install?
- 45 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does workflow need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing workflow?
- 4 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for workflow?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.