Async updates via Automated Test FrameworkIssue Async activities like workflow, BR's etc triggered by an automated test may not complete within the time frame of the test execution. So any step that assert on the result of these async activities may result in the automated test failure.CauseThe async activities run independently of the automated test and is not bound to complete within the test execution time frame. For example: In the example below the 'Record Query' step failed as the workflow activity that was meant to create a record ran few milliseconds after the test step : 2019-12-01 15:45:57 (078) worker.7 worker.7 txid=3ece7c1813e1 Processing step order: 19 for step config: Record Query2019-12-01 15:45:57 (095) worker.7 worker.7 txid=3ece7c1813e1 SessionDebug 'log' enabled for user: <user>2019-12-01 15:45:57 (552) worker.6 worker.6 txid=15ee305813e1 DEBUG: completed <worflow activity name>(5db7a88c133f3300a42330128144b050): event=executeResolutionWe do not encourage the use of gs.sleep in ATF, because: If you're not waiting for a specific condition that means you're wasting time if e.g. the condition is true after just 1 second. gs.sleep() does not work in scoped applications. The recommended pattern, if waiting for a record condition, is to use either "Record Query" or "Record Validation" with a timeout (wait until a specific record exists or until the record reaches a specific state). If you only have to perform something that requires scripting, you should instead use sn_atf.AutomatedTestingFramework.waitOneSecond(), which both: Does not let you wait more than one second and therefore forces you to break out as soon as your condition is true.Works in scoped applications.