The job is being queued to prevent a failed status, is my interpretation correct that you want to actively backup changed files with a new backup job whilst the previous job is still running?

If this is the case I think you need to validate if 10 minutes is a viable timeframe with your current configuration. How long does a backup generally take currently?

In general you can also change settings to possibly, depending on system resources, shorten time needed for a backup:

• Allow multiple data readers within a drive or mount point
• Automatically use optimal number of data readers

https://documentation.commvault.com/11.24/expert/10979_setting_data_readers_for_file_system_agents.html

Or increase network agents from default 2 to 4:

https://documentation.commvault.com/11.24/expert/7124_setting_network_bandwidth_and_network_agents_for_data_protection_operation.html

Dont use the throtteling described on this page btw.
Also keep your resources in check on the client whilst testing a backup with these settings, if you do not have enough resources your application/OS/network connection can have some response issues.

You could uncheck this option, if it’s enabled, to stop queueing the jobs.

https://documentation.commvault.com/2022e/expert/6399_job_controller_online_help.html
 

Thanks,
Scott
 

You could uncheck this option, if it’s enabled, to stop queueing the jobs.

https://documentation.commvault.com/2022e/expert/6399_job_controller_online_help.html
 

Thanks,
Scott
 

This would be my guess. We do this with some logs and such