# Polling URL using 'until' loop - how to get feedback during the loop

**URL:** <https://forum.ansible.com/t/polling-url-using-until-loop-how-to-get-feedback-during-the-loop/23398>\
**Category:** Ansible Project\
**Created:** [January 6, 2017, 2:08pm UTC](https://forum.ansible.com/t/polling-url-using-until-loop-how-to-get-feedback-during-the-loop/23398 "2017-01-06T14:08:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dick\_Visser](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@Dick\_Visser](https://forum.ansible.com/u/Dick_Visser)\
**Post date:** [January 6, 2017, 2:08pm UTC](https://forum.ansible.com/t/polling-url-using-until-loop-how-to-get-feedback-during-the-loop/23398/1 "2017-01-06T14:08:09Z")

</div>

Hi

My playbook imports a backup that takes a while, and that needs to be  
finished before I continue with the rest.  
I have created this task:

- name: "Poll backup import process"  
&nbsp;&nbsp;uri: url=[http://localhost:8090/setup/longrunningtaskxml.action?taskId=\](http://localhost:8090/setup/longrunningtaskxml.action?taskId=%5C){{  
taskid }}  
&nbsp;&nbsp;&nbsp;&nbsp;HEADER\_Cookie="{{ wizard.set\_cookie }}"  
&nbsp;&nbsp;&nbsp;&nbsp;status\_code=200  
&nbsp;&nbsp;&nbsp;&nbsp;return\_content=yes  
&nbsp;&nbsp;register: longrunner\_status  
&nbsp;&nbsp;until: "'\<currentStatus\>Complete.\</currentStatus\>' in  
longrunner\_status.content"  
&nbsp;&nbsp;delay: 5  
&nbsp;&nbsp;retries: 1000

This works great.  
But, during this task there is no output.  
And because it takes a while, with lots of retries, the screen is  
empty after a while, so it's hard to tell what's happening.

Is there a way to have output during the loop?

Thanks

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [January 6, 2017, 4:16pm UTC](https://forum.ansible.com/t/polling-url-using-until-loop-how-to-get-feedback-during-the-loop/23398/2 "2017-01-06T16:16:51Z")

</div>

There was a bug on displaying retries, that should have been fixed in current versions.