webmethods synchronous message- problem with orphan messages

we have sync messaging queues for request reply. what are the solutions to process the orphan mq response messages. Orphan messages are those that stay in the reply queue but no one is reading it because the sync call timed out after putting the message in the queue.
The response that were delayed needs to be picked up and stored in a database.
Could peek service be used here ?
Also, the request response is a set of sync queues for the synchronous messaging.