A finalized RADIUS packet is immutable and cannot be staged again

Logged when a policy action tries to stage a change to an outgoing RADIUS request or reply after Radiator has finalized it for transmission. Radiator retains the finalized packet even when submitting it to the transport fails, so a Radconf fallback that modifies and retries the same packet can also cause this event. Normal failover between configured RADIUS backend servers builds an independent upstream request for each attempt and does not cause this event by itself. The @pre-proxying pipeline runs once while constructing a request for a selected backend server; transport retransmissions reuse that result without running the pipeline again. If failover selects a different backend server, Radiator constructs a server-specific request and runs its @pre-proxying pipeline. The @post-proxying pipeline may modify the fresh radiusproxy.reply created from a received reply. These pipelines can cause this event only if they instead modify a finalized parent radius.request or radius.reply.

Complete direct modifications to radius.request or radius.reply before sending that packet. For RadSec fallback, configure multiple RADIUS backend servers with server-selection fallback, or use separate Radconf backend actions; Radiator constructs an independent upstream request for each backend attempt. Final policies may inspect finalized packet values but must not change them.