This is an expected behavior. Edit the schedule of the full backup job for the above scenario instead of placing the job on hold.

If a scheduled full backup job did not run at the scheduled time as the job was placed on hold, the subsequent incremental or differential backup job does not run and is set to the 'Superseded' status when the scheduled time comes. Here is the possible scenario to run into this issue.

1. Full backup job is scheduled every 1 week on Friday at 11pm
2. Incremental backup job is scheduled every 1 day at 11pm

Due to some reasons, the full backup job needs to run on Friday at 9pm instead of 11pm. In this case, the scheduled job can run at 9pm by manually clicking 'Run Now' and the job is placed on hold to avoid running the job again at 11pm. On Saturday its associated incremental backup job does not run and it is set to 'Superseded' status.