There is currently no way to know what node is currently being executed / how far along it is. This information is delivered over WebSocket.
This should probably be a callback for the functions that queue workflows? but I also suspect there are greater implications for the API design once WS support is in.
Depends on #3.
There is currently no way to know what node is currently being executed / how far along it is. This information is delivered over WebSocket.
This should probably be a callback for the functions that queue workflows? but I also suspect there are greater implications for the API design once WS support is in.