# Include\_tasks docs lack info on tail recursion **URL:** \ **Category:** Project Discussions\ **Tags:** include\_tasks, playbook, documentation\ **Created:** [November 12, 2023, 2:02pm UTC](https://forum.ansible.com/t/include-tasks-docs-lack-info-on-tail-recursion/2306 "2023-11-12T14:02:16Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [November 14, 2023, 2:43am UTC](https://forum.ansible.com/t/include-tasks-docs-lack-info-on-tail-recursion/2306/5 "2023-11-14T02:43:12Z")
hi @utoddl I seen no reason for Ansible to preemptively restrict that use of `include_task`. However, I must say that using Ansible as a _programming language_ is not something I would be very keen about. To solve your problem, I would try and look into using `strategy` as @tanganellilore recommended in [Async task / queue management - #2 by tanganellilore](http://forum.ansible.com/t/async-task-queue-management/2296/2) As of the documentation for `include_task` I reckon that recursion (whether it’s tail or not) could be added, but IMHO it should come with a big warning saying that although this is not restricted, one should be _ **extremely** _ careful doing that. Just my $0.02 --- _[View the full topic](https://forum.ansible.com/t/include-tasks-docs-lack-info-on-tail-recursion/2306)._