Closed
Description
Right now finalTimeout
just sets a setTimeout
, but doesn't actually enforce a maximum transaction length. This means there are some scenarios where a transaction has started, but has a super long duration (1 min+).
If we see that a transaction's duration has exceeded the final timeout, we should drop it, because it means that the duration is effectively invalid (didn't respect setTimeout
of finalTimeout
).
┆Issue is synchronized with this Jira Improvement by Unito