We are getting NATS JetStream errors - stream names with @ or . are rejected. How do we fix this?

This is a known issue. Tazama processors generate stream names in the format (dynamically constructed in the processor as rule-901's subscription subject for the v4.0.0 rule processor), which contains characters that NATS JetStream does not allow. JetStream was implemented as an option for the internal Tazama data flows, but abandoned during our performance improvement and benchmarking project ahead of Release 2.1.0. The ability to select NATS JetStream in release 3.0.0 has been deprecated, but the removal of the functionality remained as technical debt until release 4.0.0 when it was scrubbed entirely, along with the environment variable to select the startup type. Tazama is currently designed around NATS-based routing exclusively. The Tazama Technical Steering Committee is evaluating an approach that can accommodate both in a future release.