> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/unable-to-retrigger-a-an-existing-pipeline-from-spinnaker-ui.md).

# Unable to retrigger a an existing pipeline from Spinnaker UI

### Issue <a href="#issue" id="issue"></a>

Users may run into a situation where they may be unable to re-trigger a pipeline through the Spinnaker UI. It is noticed that the UI is not responsive when such pipelines are triggered.

### Cause <a href="#cause" id="cause"></a>

An application in Armory Enterprise Spinnaker is created through one of the following methods

* Using Spinnaker UI where they create the application using the Deck web console.\* Invoke the Front50 API directly.\* Use Armory's Pipeline As Code feature (Dinghy). The ***Application names are generally expected to be with lowercase***. Even if they are to be created with uppercase through the UI, the Deck and the Gate Spinnaker services convert them to lowercase before they are persisted by Front50. However if the applications with their names in uppercase are created using Front50 API or Dinghy, they get persisted as they are without any validations or conversions. When pipelines belonging to such applications are triggered through the Spinnaker UI, it ***fails to find the application*** as the original application created is with uppercase.