Sybase Replication Warm Standby : how long does a transaction remains in the LDS inbound queue

I am replicating data from sourcedb1 (syb ASE AIX 1254 2k pages) to targetdb1 (syb ASE linux 1254 2k pages) and recently we added targetdb2 (syb ASE Linux 157 8k pages)

targetdb1 only contains a subset of table and targetdb2 is a warm standby database.

When I execute larger transactions, there are executed fast on both target servers, no issues.

But the inbound queue of my LDS keeps this transaction long time and is using disk space. My monitoring script assumes that there is a large backlog. 150000 record inserts arrives in seconds on both target servers, but takes over 15 minutes to be removed to be removed from the inbound LDS queue.

How long does replication server stores this information in the inbound stable queue? And is there a way to control this?

Best regards,

Toon Eysakkers