iwf

iWF is a Workflow-As-Code microservice orchestration platform offering an orchestration coding framework and service for building resilient, fault-tolerant, scalable long-running processes

Runs with mockssource: GitHubGoMITcommit ad3d109fd9d8

Go, MIT licensed. The project labels itself: distributed process, distributed system, distributed transactions, durable timer, golang, java, message queue and microservice.

iwf runs, with stand-ins for the services it depends on. An Argusic agent installed it in 16 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

iwf-server binary builds, all 23 unit tests pass, blobstore integration tests pass against moto S3 mock, and the server starts on port 8801 connected to a local Temporal dev server, responding with HTTP 200 on healthcheck and workflow start API.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
663
forks
62
open issues
79
watchers
19
size
13 MB
created
last push

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.

Time lost to each failure while testing iwf, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • S3/MinIO endpoint refused on port 90004 minutes
  • Temporal dev server kept dying after backgrounding2 minutes
  • Go 1.24 not installed in container1 minute
  • iWF could not reach Temporal after session exit1 minute
  • iWF could not connect to Temporal due to IPv6 resolution of localhost1 minute
  • Workflow start returned 500 due to missing search attributes1 minute
Install time
16 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
curl http://127.0.0.1:8801/info/healthcheck returned HTTP 200 with condition OK; curl POST /api/v1/workflow/start returned HTTP 200 with a valid workflowRunId; go test ./service/... all 23 tests PASS; go test ./service/common/blobstore/ all 8 subtests PASS
Model tokens used
613,832
Exact commit tested
ad3d109fd9d8
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

| `TestBlobStoreIntegration` failed — S3 endpoint (MinIO on `localhost:9000`) refused connection | …
| Temporal dev server kept dying after process backgrounding — `nohup` + `setsid` were insufficient…
| iWF server connected to Temporal on first attempt; subsequent launches failed with "connection re…
| iWF server could not connect to Temporal — Go resolved `localhost` to IPv6 `::1`, but DB file sti…
| Workflow start returned 500 — required search attributes `IwfWorkflowType`, `IwfGlobalWorkflowVer…
**Total time lost to errors: ~9 minutes**
## What was verified
- **`make bins` (build)**: `go build -o iwf-server cmd/server/main.go` — exited 0, produced a 64 MB…
- **Unit tests** (`go test ./service/...`): All 23 tests PASS, 0 failures.
- **Blobstore integration tests** (`TestBlobStoreIntegration`): All 8 subtests PASS against moto S3…
- **iWF server healthcheck**: `curl http://127.0.0.1:8801/info/healthcheck` returned `{"condition":…
- **Workflow start API**: `POST /api/v1/workflow/start` returned HTTP 200 with `{"workflowRunId":"0…

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

  • Installed in 16 minutes.
  • Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.03

Topics (from GitHub)

distributed-processdistributed-systemdistributed-transactionsdurable-timergolangjavamessage-queuemicroserviceorchestrationorchestratorpersistenceprocesspythontimerworkflowworkflow-as-codeworkflow-engine

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/iwf.svg)](https://argusic.com/subject/iwf)

Questions

Does iwf run?
iwf runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 16 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test iwf?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ad3d109fd9d8. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test iwf?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does iwf take to install?
16 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 iwf need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing iwf?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for iwf?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion