the root issue is that subordinate service is not appearing in the watch output, which is a bug in core. deployer tries to do some workarounds on watches to ensure its consistent by waiting for 5.1 seconds (implementation details on core which may have changed). status is implemented via api by core for a while now, so the other work around is to try and use that api instead of the watch.
the root issue is that subordinate service is not appearing in the watch output, which is a bug in core. deployer tries to do some workarounds on watches to ensure its consistent by waiting for 5.1 seconds (implementation details on core which may have changed). status is implemented via api by core for a while now, so the other work around is to try and use that api instead of the watch.