** CLI Version ** * Hit `rivery --version` and copy here. 0.3.3 **Describe the bug** A clear and concise description of what the bug is. When hitting the `rivery river run fire --riverId=<riverId> --waitForEnd` it seems like there's a `timeout` without default issue there. **To Reproduce** try to hit ```bash > rivery river run fire --riverId=<river id> --waitForEnd ``` **Expected behavior** The --waitForEnd should end for end of the run :) ** OS ** Win 10