SwishrJobs
•

Reliability

How often the work actually succeeds, measured rather than claimed. These are controlled synthetic results, never customer outcomes, and a capability that has not been measured shows no rate at all.

Measured
nothing yet
Capabilities
0 of 23
Source
no stored benchmark report

No benchmark has been run on this build, so no success rate is published and no placeholder is shown. Every capability is listed as not measured. Run swishrjobs benchmark --state-dir <dir> to measure this deployment.

CapabilitySuccess rateSampleFailures
boundary-value-generationnot measured——
csv-json-transformationnot measured——
data-validation-modulenot measured——
dataset-quality-reportnot measured——
duplicate-group-reportnot measured——
edge-case-checknot measured——
field-mappingnot measured——
json-csv-conversionnot measured——
json-schema-inferencenot measured——
key-normalisationnot measured——
malformed-record-detectionnot measured——
markdown-table-renderingnot measured——
metadata-extractionnot measured——
nested-flatteningnot measured——
python-multifile-packagenot measured——
python-utility-modulenot measured——
readme-generationnot measured——
record-deduplicationnot measured——
regex-from-examplesnot measured——
regression-suite-generationnot measured——
text-parser-modulenot measured——
webhook-payload-validationnot measured——
xml-json-conversionnot measured——

Success means the job completed and the independent verifier accepted the artifact; for a refusal case it means the service rejected the request as invalid input. A rejection caused by an unavailable provider or a closed gate counts as a failure, never as a successful refusal. GET /v1/performance · Status