Thank you Alex, how can I modify the OnFailureTimeout method for my purpose? I can find only a little documentation

Thank you Luis, this was useful. 

However, I've encountered two issues while adapting the code you provided to my specific situation:

if ..RetryCount = 1 {
    ; Find the production
    #dim p As Ens.Config.Production
    Set p = ##class(Ens.Config.Production).%OpenId("ProductionName")
    if '$isObject(p) {
        $$$LOGERROR("Production not found")
        quit
    }
    #dim item As Ens.Config.Item
    #dim sett As Ens.Config.Setting
    ; Loop over all the elements of the production 
    for i=1:1:p.Items.Count() {
        s item=p.Items.GetAt(i)
        ; Find the desired business component
        if (item.Name="Component1Name"
            ||(item.Name="Component2Name"))
            {
            $$$LOGINFO(item.Name_" found")
            ; Explore settings
            for s=1:1:item.Settings.Count() {
                set sett=item.Settings.GetAt(s)
                ; Search for the FailureTimeout
                if (sett.Name="FailureTimeout"){
                    $$$LOGINFO(sett.Name_" found")
                    ; Change the valure of the FailureTimeout based on the Severity
                    If Severity = "high" {
                        set sett.Value = -1
                    } Else {
                        set sett.Value = 30
                    }
                } 
            }
        }
    } 
    Set sc = p.%Save()
    If $$$ISERR(sc) { 
        $$$LOGERROR($System.Status.GetErrorText(sc))
        quit
    } 
}

With this code, I can adjust the FailureTimeout value based on the Severity parameter, and the updated value is correctly shown in the Production settings. Nevertheless, there are a couple of issues:

1. This functionality only applies to modified settings, as it doesn't affect settings with default values, which are not included in the loop (set sett=item.Settings.GetAt(s)). Consequently, it's necessary to modify the settings at least once to ensure they are processed within the loop.
2. While the FailureTimeout value gets updated, the sending procedure uses this updated value for the subsequent message, not the current one. As a consequence, the current message continues to operate with the outdated FailureTimeout value, causing the sending (and re-sending) procedure to deviate from the desired timeouts. 

Hi Rich, sorry for the late response but I've worked on other projects for some times.

I believe the issue with my code lies in the fact that the POST request was sent via a %Net.HttpRequest object:

// Send an HTTP POST request
Set messageStatus = httpRequest.Post(operation)

rather than using directly the adapter: 

set tsc = ..Adapter.PostURL(URL,.tResponse,,InputStream)

so the Timeout property of the %Net.HttpRequest object wasn't affected by the change on Response Timeout.

I solved this issue with a little help of @Menno Voerman's suggestion:

Set tHttpRequest.WriteTimeout = ..Adapter.WriteTimeout
Set tHttpRequest.Timeout = ..Adapter.ResponseTimeout
Set tHttpRequest.OpenTimeout = ..Adapter.ConnectTimeout  

In this way is possible to modify the response timeout dinamically too. 

I'm not sure if switching to the Adapter.PostURL method is a better choice compared to using httpRequest.Post. For now, I'm using the latter to minimize changes in my code.

Thanks Tani, this was very helpful!

Thanks for the suggestion, I will!

Thanks Evgeny, this is a good solution for who use Docker!

Thanks John, this is an interesting feature! Unfortunately I've only IRIS 2021.1 😓

Thank you Menno for this interesting solution. If I can't resolve the issue using my method, I will try to adapt your solution to my case.

Thanks for the feedback. I tried setting Connect Timeout and Response Timeout as adapter's properties and Reply Code Actions, Retry Interval, and Failure Timeout as Business Operations' properties, in this way: 

    Set ..Adapter.ConnectTimeout = 15
    Set ..Adapter.ResponseTimeout = 10
    Set ..RetryInterval = 5
    Set ..FailureTimeout = 60
    Set ..ReplyCodeActions = "E=R"

But nothing changes if I modify the parameters, as the BO uses only the values defined in the Production Settings (even if they are all blank).

I tried, but only the message that received a reply is displayed. 

edit. I also tried with the BO parameter "RetryCount", for example: 

    $$$TRACE(..RetryCount())

but this property is a boolean variable and so I always get print "1". In the same way, I also tried the methods RetryCountGet(), which always print me "1", and RetryCountLogicalToDisplay(), which always print me "96".

Thank you! Is it possible to set these parameters by code? I need to include many similar Business Operations to contact different entities, and I would like to set default parameters so that I don't have to change them every time I add a new BO.

Thank you! With these settings and with a delay of 12 seconds of the Postman Mock Service, the BO correctly resends the message. However, I can't see the resent messages in the visual trace but only a message, as it happens when the message is not resent. Is there a way to see the resent messages as well or at least to see a warning or a log telling us that the BO is trying to send the message again?