How does the "time limit (hours)" setting in Scheduled Task work?

[Weilong Li]

My native language is not English, and all texts are translated through AI, so there may be errors. I apologize in advance for any inaccuracies.

In Scheduled Task, there is a "time limit (hours)" setting. How does it work? (Or, what is its function?)

Does it mean that when "time" expires, the task is executed, and then it needs to wait for the duration set in "time limit (hours)" before restarting the calculation of "time"?
Or, when the "time" expires, both the "time" and the "time limit (hours)" start to be calculated simultaneously, and the task will only be executed if both exceed their time limits?
Or is it used only to set an interval time to prevent frequent execution, where the Scheduled Task will only execute if the interval between two times is greater than the "time limit (hours)"?
Or is there some other function that I haven't thought of?

[TheDreadPirate]

If a task takes too long to complete this setting will kill the job after the configured amount of time. Some tasks, like creating trickplays, can take many hours to complete when you add a lot of content. Audio normalization can also take a long time. And both of these examples can use a lot of CPU power. If you have a jellyfin server with limited compute power these two jobs could affect the usability of Jellyfin.

So to account for your limited CPU resources you want these jobs to run at 1 am when no one is using the system. But you want to kill the job after 5 hours (6am) when you/your users wake up and may start using Jellyfin.