This message was deleted.
# getting-starteds
sparse-intern-71089
10/21/2022, 6:55 PMThis message was deleted.
l
little-cartoon-10569
10/21/2022, 7:13 PMThis tends to happen to me because promises are leaking. Check your code for unresolved promises?
f
few-carpenter-12885
10/21/2022, 7:15 PMI can most-definitely put a try-catch around the stack.up() call that I'm making. Is this just simply a catch and retry the call type of scenario?
few-carpenter-12885
10/21/2022, 7:16 PMI'm trying to use the automation API in a self-serve capacity, so ideally I'd like to do as many checks beforehand to avoid something like this.
l
little-cartoon-10569
10/21/2022, 7:19 PMThat might help, I don't know enough about how to clean up promises. In my context, it's always due to an exception being thrown and the engine or unit test context ending prematurely. So putting a catch in the right place might help. It would probably have to be inside the stack/project code though, rather than around it?
f
few-carpenter-12885
10/21/2022, 7:21 PMAh, that makes much more sense. I hadn't thought of adding catches or checks inside the program function - that may be what I'm looking for. I'll give that a shot, thanks 👍
12 Views