We have a few transactions that require a few successful button clicks in order for the transaction to fully succeed. While successful 95% of the time, we get enough back to back failures which will trigger our email alert (down for 10 minutes) when the application is actually online. I opened a case with Solarwinds Support, but the only two options are the standard button click or the XY coordinates. While the XY coordinates helped decrease the amount of failures, it still occurs back to back 1-2 times a day. We can extend the email alert to trigger after 15 or 20 minutes (3 failed transaction plays), but in an actual application down scenario we wouldn't be aware of the outage until 5 or 10 minutes later.
Would it be possible to add an option to attempt the same failed step 'x' number of tries or start the transaction 'x' number of times from the start before classifying the transaction as down? The current options of making parts of the transaction conditional/optional would not work for us as we need to confirm all parts of the application are online to classify with an 'up' status.
