# Using "short lived facts" and caching, Eg. ansible\_uptime\_seconds

**URL:** <https://forum.ansible.com/t/using-short-lived-facts-and-caching-eg-ansible-uptime-seconds/44324>\
**Category:** Get Help\
**Tags:** facts, ansible-core\
**Created:** [August 19, 2025, 5:26am UTC](https://forum.ansible.com/t/using-short-lived-facts-and-caching-eg-ansible-uptime-seconds/44324 "2025-08-19T05:26:04Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![flowerysong](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/flowerysong/32/2305_2.png) [@flowerysong](https://forum.ansible.com/u/flowerysong)\
**Post date:** [August 19, 2025, 11:33pm UTC](https://forum.ansible.com/t/using-short-lived-facts-and-caching-eg-ansible-uptime-seconds/44324/5 "2025-08-19T23:33:14Z")

</div>

> [@James\_Antill](#):
>
> As far as I can see this still uses the cache, like having `gather_facts: true`

It does not. Cached facts only prevent automatic running of `gather_facts` when `DEFAULT_GATHERING=smart`, they have no effect on explicit fact gathering in a task. See [I don't understand gather\_subset - #12 by flowerysong](https://forum.ansible.com/t/i-dont-understand-gather-subset/6660/12)

---

_[View the full topic](https://forum.ansible.com/t/using-short-lived-facts-and-caching-eg-ansible-uptime-seconds/44324)._