# Command hangs when promoting release

**URL:** <https://community.convox.com/t/command-hangs-when-promoting-release/537>\
**Category:** Rack (Version 2)\
**Created:** [May 22, 2019, 11:32am UTC](https://community.convox.com/t/command-hangs-when-promoting-release/537 "2019-05-22T11:32:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![operations](https://avatars.discourse-cdn.com/v4/letter/o/b487fb/32.png) [@operations](https://community.convox.com/u/operations)\
**Post date:** [May 22, 2019, 11:32am UTC](https://community.convox.com/t/command-hangs-when-promoting-release/537/1 "2019-05-22T11:32:13Z")

</div>

When trying to promote a release using `convox releases promote`, the output hangs on `system/aws/cfm staging-mathematics-mastery CREATE_COMPLETE RecordSetWebInternal`, and the release does not get promoted. No error message are given, the command just does not complete.

Where would it be possible to find logs which could give insight into why the command is having problems at this stage? Thank you.

---

<div class="post-metadata">

**Author:** ![operations](https://avatars.discourse-cdn.com/v4/letter/o/b487fb/32.png) [@operations](https://community.convox.com/u/operations)\
**Post date:** [May 22, 2019, 11:37am UTC](https://community.convox.com/t/command-hangs-when-promoting-release/537/2 "2019-05-22T11:37:01Z")

</div>

To give some more background information, it appears that the build completes successfully, however no web service is created, although it is defined in convox.yml.

We are trying to deploy to a staging rack. The same web service is running already on a production rack without issue.

---

<div class="post-metadata">

**Author:** ![vincent](https://avatars.discourse-cdn.com/v4/letter/v/e9bcb4/32.png) [@vincent](https://community.convox.com/u/vincent)\
**Post date:** [May 22, 2019, 12:18pm UTC](https://community.convox.com/t/command-hangs-when-promoting-release/537/3 "2019-05-22T12:18:05Z")

</div>

You can find the AWS CloudFormation stack and check which resources are in CREATE\_IN\_PROGRESS or UPDATE\_IN\_PROGRESS state.

That may guide you towards an underlying issue.
