Just because UC4 can do it, doesn't always mean it should. It is a bad solution design when it demands the batch scheduler run a batch program so frequently that it simulates near-real-time service. This is not the best use of your batch scheduling system.
At this datacenter we push back and tell them that if they need their process to run more frequently than once every 30 minutes, then they really need a better design. To some designers, expecting UC4 to do this process is a convenient short cut by making it your design problem instead of their design problem.
To run an application every 30 minutes, we only need to create 48 schedule entries. (We have several like this.)
One solution I like is to have the application invoke CALLAPI to tell UC4 exactly when the job needs to be executed. Another viable solution is to have them build their own web service to handle the iterative processing that needs to take place.