test_fixture_not_fixture: The stream does not pay a test service node
POST /owner/v1/test-fixtures/streams/{id}/run was called for a Control Mode stream whose service node is not one of the test service nodes listed by GET /owner/v1/test-fixtures (approve, refuse, slow, dispute, settlement_fail). Only those five addresses have a fixture behaviour; an unused address in the reserved range has none either. Nothing is metered.
The multi-tenant hosted tier answers the same way: the front door passes the request to the account's core.
What to do
- Open the stream to one of the listed fixture addresses, then run the delivery on that stream.
- For a real payee, meter through the plugin wire or the SDK instead.
- See test agents and payees.
On the wire
HTTP 409, error type state_error, param: "id".
{
"error": "state",
"errorDetail": {
"type": "state_error",
"code": "test_fixture_not_fixture",
"message": "the stream's service node is not a reserved test service node",
"param": "id",
"doc_url": "…/developers/testing.md#test-fixture-not-fixture",
"fix": "the stream's service node is not a reserved test service node"
}
}
A stream on a money-mode budget answers test_fixture_money_mode first. See all error codes.