The NATS-backed streaming transport became unavailable while running a streaming compute subscription.
This can happen during a NATS pod rollout after the streaming compute restart budget is exhausted.
Clients may retry by recreating the subscription. This uses INTERNAL because custom Conjure errors in this
API do not support an UNAVAILABLE code; consumers should branch on this error name rather than HTTP status.