We have a library that contains a workflow for an application log in. In the master workflow that was compiled into the library package there are timeouts attached to several steps that we assumed would cause the robot to error out if those timeouts were exceeded. This does not appear to be the case when running the activity after downloading the package - it goes on forever.
Is there a way to add a Timeout to the activity - or does someone know a good way to force an error to be thrown if the activity runs for too long?