queues importantWritten by the Hub
Where this message's results go
Result queue names for this message alone, overriding the node's success and failure.
In detail
Solves the exclusivity problem described in the queues chapter. Results are removed by whoever reads them first, so Hub and a customer's application cannot both consume the node's queues — but a customer's messages can carry their own queue names, leaving the node's defaults entirely to Hub. That makes this property the mechanism for running a shared node honestly: our telemetry stays complete, and the customer gets their own stream with no contention.
What happens if you get it wrong
Results directed to a queue nobody consumes.They accumulate exactly like the node's own queues, with the same effect on the broker.inference · inference