# (1.2) skipped tasks now work with register

**URL:** <https://forum.ansible.com/t/1-2-skipped-tasks-now-work-with-register/12728>\
**Category:** Ansible Project\
**Created:** [April 28, 2013, 1:56pm UTC](https://forum.ansible.com/t/1-2-skipped-tasks-now-work-with-register/12728 "2013-04-28T13:56:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [April 28, 2013, 1:56pm UTC](https://forum.ansible.com/t/1-2-skipped-tasks-now-work-with-register/12728/1 "2013-04-28T13:56:25Z")

</div>

It’s been frequently requested that we needed a better way do this:

- action: service name=foo state=running  
register: some\_result  
when: x == 3

- action: shell echo ‘some random example’  
when: some\_result.changed

However, before this could not be done easily, as ‘skipped’ tasks (when x was not 3) did not register variables, so you could not access some\_result.changed consistently.

I have now fixed the glitch so the above example works.