Forward Dead lettering Messages when destination topic having issue

[yandrapragada]

Actual Behavior

I have a topic which has a subscription with Forward Dead lettering Messages to another topic. In scenarios like reaching maximum delivery count, message will be moved to DLQ. Since Forward To is enable on DLQ it has to forward all the messages it received on to the new topic. Let say if the destination topic is disabled/inactive or reached its max available size ,the message will remain in the DLQ only. It is not possible to create a receiver when Forward To is enabled. So these messages are neither can be read by creating a receiver on DLQ nor on the destination topic. Looks no provision to receive these messages.

Expected Behavior

1. Provide a provision to read these stuck messages.
2. Alternatively, any re try mechanism to send these stuck messages to the destination topic at later time like once the topic is active forward old stuck messages as well to destination topic.

[EldertGrootenboer]

There is no additional logic needed for this. In case the destination entity is disabled, forwarding to this entity will still continue to work. When the destination entity has reached it's maximum available size limit, the messages will remain in the DLQ on the origin entity until the destination entity is cleaned up, at which point the messages will be forwarded again from the origin DLQ to the destination entity.