Retries / Status Checks / Timeouts
A common setting to configure when managing deployments is setting intervals for system checks. An interval-based process is something that happens repeatedly until it no longer needs to do that check or activity. This could be "How often should the system check if a status has changed?" and could be accompanied by "How long should I do this interval process for?".
There are two approaches you can consider for this problem.
Select (drop down) Approach
The select option is favourable due to common sensible defaults. As a user, I don’t need to think too hard about how much time to put in. This is useful because it sets good guardrails as to what information is selected and gives limited choices so that it's easier for the customer to make a selection. In addition, we can add a clear "zero" state of "No timeout" limiting the number of fields needed.
If you really need to supply a custom timeout, this is still a possible addition.
Input Approach
Alternatively, if having a textField with type=number, with a single common default. This works well if there aren't a good group of common defaults that could apply and customers' needs are quite varied. Typing a number is easy to do.
The downside of this scenario is if I wanted to try 5 mins using the input in seconds version I would have to calculate those numbers which is more mental work for the customer. You may use multiple inputs in this instance.
Avoid using steppers
Steppers are ideal for changing small increments, such as adding 3 bananas for online grocery shopping or allocating 2 tickets for a concert purchase. Steppers typically have small limits. See the NNGroup article on steppers.
Always consider the user's needs
This is one of those it depends situations so take time to consider what information the user going to be inputting. In addition, consider what is a good sensible default and what are some sensible guardrails such as defining a max limit.