Some user interactions can be assigned an extra status based on its outcome:
- Failed, indicating that the interaction did not complete as expected due to technical errors. This status is set if at least one of the HTTP requests during the user interaction responded with a 400 or 500 series error code.
- Stuck, set when the duration of the ongoing interaction exceeds the predetermined slow threshold by more than 100x. In this case Plumbr assumes the transaction will never complete and flags the transaction as Stuck. Plumbr will stop monitoring the stuck transaction after flagging it as such.
Status flags for API calls work similarly.