Similar issue is reported in Bug which was suspended due to some reasons.
You can try to ignore the problematic DDL transaction which is causing the issue.
Please confirm if your replication setup is DML only or both DDL and DML.
Apply process will move this state "PAUSED - WAITING FOR DDL TO COMPLETE" only when DDL operations are performed at Source database.
It will catch up as soon as the DDL transaction is completed.
Either you can ignore this transaction and manually perform DDL on target .
Tag the DDL transaction so that it is not captured by Capture process and manually perform DDL on target .
Wait for the Apply process to complete its task.