Hi @michael_soprano ,
I do not think you cant create that sort of dependency within AEP query service.
However, if this is your goal, I would suggest:
- Easiest option: put everything in a single query. The whole script will be divided into 3 blocks where each block will check the previous block's success status (you have to keep log may be in a separate dataset) and only proceed then
- Lengthy process: you can use middleware instead of a single query. The 3 queries will be scheduled. The middleware can try to retrieve the status from a query and depending on the "Success/ Falied" the middleware can delay / cancel the next one's run (document is there, but I have not done it, so needs to be thought of with care)
I would say try to go for #1 - in that case, every block will store start & end of every block in a single log dataset which will be retrieved before execution of the next block!
Hope this helps!
