Exceeding max queue spool blocks publishers?

If a client creates a queue with a topic subscription and then does not consume the queue for whatever reason, it will eventually reach its max spool usage. At this point anyone attempting to publish guaranteed messages to that topic will fail. Is there any way to prevent this publishers from being impacted in this situation? I'm new to Solace PubSub+, but this seems like a large risk for a single consumer to be able to block publishers. Ideally I'd like incoming messages to be discarded for the problem queue, or new messages to replace the oldest message in the queue.