# Workflow doesn't recognizing prompt on launch.

**URL:** <https://forum.ansible.com/t/workflow-doesnt-recognizing-prompt-on-launch/35072>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [April 27, 2021, 8:08pm UTC](https://forum.ansible.com/t/workflow-doesnt-recognizing-prompt-on-launch/35072 "2021-04-27T20:08:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thiago\_Castro](https://avatars.discourse-cdn.com/v4/letter/t/f6c823/32.png) [@Thiago\_Castro](https://forum.ansible.com/u/Thiago_Castro)\
**Post date:** [April 27, 2021, 8:08pm UTC](https://forum.ansible.com/t/workflow-doesnt-recognizing-prompt-on-launch/35072/1 "2021-04-27T20:08:57Z")

</div>

Hey, Guys.

Recently, I’ve updated my AWX environment from 6.0 (lol) to 19.0

I’ve done a clean installation of 19.0 and imported the projects, workflows, jobs, etc… through tower-cli.

My workflow templates are ignoring the limit flag configured on the jobs.  
When I add the job template on the workflow, he asks me for the LIMIT (the prompted option) and I configure with my parameteres. But, when I run the workflow, the workflow job ignores the LIMIT configuration I’ve put before and try to execute the job at the inventory.

Fun fact: I have 3 workflows. One of them works perfectly, the two anothers are bugged.

I tried to create another workflows for testing purposes, but I had no success.

Can you guys help me? I had to create a job template for every server, hard coding the servername on the limit flag so I can deploy our application in our servers.

Regards,  
Thiago.

---

<div class="post-metadata">

**Author:** ![mabashia](https://avatars.discourse-cdn.com/v4/letter/m/e9a140/32.png) [@mabashia](https://forum.ansible.com/u/mabashia)\
**Post date:** [April 27, 2021, 8:12pm UTC](https://forum.ansible.com/t/workflow-doesnt-recognizing-prompt-on-launch/35072/2 "2021-04-27T20:12:29Z")

</div>

Sounds kind of like [https://github.com/ansible/awx/issues/9377](https://github.com/ansible/awx/issues/9377)

---

<div class="post-metadata">

**Author:** ![Thiago\_Castro](https://avatars.discourse-cdn.com/v4/letter/t/f6c823/32.png) [@Thiago\_Castro](https://forum.ansible.com/u/Thiago_Castro)\
**Post date:** [April 28, 2021, 6:11pm UTC](https://forum.ansible.com/t/workflow-doesnt-recognizing-prompt-on-launch/35072/3 "2021-04-28T18:11:54Z")

</div>

Thx for your reply. That issue describes exactly my problem. I got a workaround for this:

Create your workflow, configure your nodes. Save your configuration

Update your workflow through the AWX API:

PUT http://{your\_awx\_url}/api/v2/workflow\_job\_templates/{your\_workflow\_id}/ HTTP/1.1  
Authorization: Basic your\_username:your\_password  
Content-Type: application/json

{  
“name”: “Your workflow name”,  
“limit”: null,  
“scm\_branch”: null,  
“ask\_variables\_on\_launch”: true  
}

(I used vscode rest api for run this code, you can use curl for that too)

And the workflow will work as expected.

The bug consists in the AWX GUi, when you create a workflow, the default parameters are ignored, so limit, scm\_branch and ask\_variables\_on\_launch are always a blank space.  
for LIMIT variables, AWX interpreters you don’t have a LIMIT and try to execute the job on all hosts on your inventory.