What’s new

#New MSA feature: Error handling

We’ve added a new Error handling section in the MSA Visual step editor UI. This feature gives you more flexibility in handling MSA step errors, allowing better control and adaptability to dynamic web server behaviors.

Selecting the Continue execution after an error checkbox enables you to ignore errors that occurred in an MSA monitor step. This means that if a certain step encounters any errors (such as a bad request, request timeout, or failed assertion), the monitor will continue checking the remaining steps. Such errors will only be visible in the Step results and displayed as An error occurred during this step. These will not be reflected in any of your Errors overview dashboards or reports.  

This error-handling behavior is similar to that of the Transaction monitors. For more information, refer to the Using ignore errors for optional steps and actions knowledge base article.

#New TLS versions checkbox option in Multi-step API (MSA) monitors

We’ve added the TLS version(s) checkbox option in the MSA visual step editor UI.

By ticking the Only allow specific TLS versions checkbox, you can now select specific TLS versions during the TLS handshake for HTTP connection in MSA monitors. You can also uncheck the checkbox if no restrictions are needed.

All Uptrends checkpoints support TLS 1.1 and TLS 1.2. Selecting the TLS 1.3 option limits Checkpoint selection to those with TLS 1.3 capability. While TLS 1.1 is still available, it is not recommended.

#New field: Secret encoding method in vault items

The One-time password configuration vault item data type now includes the Secret encoding method field. This new field allows you to choose if secret values are encoded in either Hex or Base32 format. Previously, only the Base32 format was supported as the encoding method.