Thank you Evaldo. Unfortunately, none of your suggestions are going to work for my use case. An average test completion takes between 15 and 20 minutes but CAN take up to 120 minutes (for this test case; others may take longer than that). Additionally, if I decide to request the API status in a shorter interval, the API maintainer team is going to kill me 
For completeness sake, I’ve opened up a Github issue related to this topic: https://github.com/robotframework/robotframework/issues/4077. The only workaround that I have been able to determine (but haven’t tested yet):
- Positive Outcome exits the WUKS keyword successfully with a “success” return code (e.g. global variable)
- Negative Outcome exits the WUKS keyword successfully with a “failed” return code
- Just like before, a “test is still running” use case triggers a soft fail which will then cause a new WUKS loop.
With this scenario, code residing outside of the WUKS keyword could then evaluate the test’s result - and terminate it with a FAIL, if necessary. This approach is far from ideal but should work. I will go for this approach if there is no better solution.