test_fixture_refused: The refuse fixture refused the work
POST /owner/v1/test-fixtures/streams/{id}/run was called for a stream that pays the refuse test service node. That fixture always refuses, so you can test how your app handles a payee that turns work down. Nothing was metered or billed; the run is recorded as refused.
This is the expected answer for that fixture, not a fault. The multi-tenant hosted tier answers the same way: the front door passes the request to the account's core.
What to do
- Handle the refusal in your app the way you would handle a real payee refusing work.
- To test a delivery that succeeds, use the
approveorslowfixture. - See test agents and payees.
On the wire
HTTP 409, error type state_error.
{
"error": "state",
"errorDetail": {
"type": "state_error",
"code": "test_fixture_refused",
"message": "the refuse fixture refused the work; nothing was billed",
"param": null,
"doc_url": "…/developers/testing.md#test-fixture-refused",
"fix": "the refuse fixture always refuses; nothing was billed"
}
}
See all error codes.