We have a similar requirement in our tests with validations on 1 or more delayed events. We do it similar to the way AlexKaras said and run a number of creation tests, run some other tests then at the end of the tests run the corresponding validations. TestComplete unfortunately does not have table dynamic variables otherwise you'd be able to maintain a table to maintain the states of the different tests. For another system we have a two delays of 10 minutes which we had reduced to 5. Even then its inefficient.
Another way we do it is to create a bunch of things and update spreadsheet with their unique IDs, validation status, date-time etc. Then when the test runs it first checks the spreadsheet for past untested items then validates them updating the spreadsheet logging errors in the testlog. At the end it creates more items for future tests that will run next time around. We have 2 stages of delays so that process run again to see if the 1st stage has passed, test the 2nd stage and update the spreadsheet. For DevOps tests we can email the spreadsheet if needed.
