# Bizarre recursive place case

**URL:** <https://forum.communityhealthtoolkit.org/t/bizarre-recursive-place-case/3825>\
**Category:** Development\
**Tags:** configuration, hierarchy, contact-type\
**Created:** [August 1, 2024, 3:32pm UTC](https://forum.communityhealthtoolkit.org/t/bizarre-recursive-place-case/3825 "2024-08-01T15:32:18Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![jkuester](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/jkuester/32/806_2.png) [@jkuester](https://forum.communityhealthtoolkit.org/u/jkuester)\
**Post date:** [September 10, 2024, 1:35pm UTC](https://forum.communityhealthtoolkit.org/t/bizarre-recursive-place-case/3825/11 "2024-09-10T13:35:45Z")

</div>

As expected, I do not see anything unexpected with the household `parent` config in that form.

I guess that still brings us back to some kind of race condition between launching the form and changing which contact is in context… I have tried to recreate similar behavior by slowing down the CPU/Network and clicking around in the app, but so far I have not been successful. (This is not surprising, though. If it was easy to produce this behavior, I guess it would be much more common.)

The main lingering doubt I have is that if it is a race condition, why has it only been observed in this deployment? With that prompting some more out-of-the-box thinking, there is no chance that you might have some [dynamic url linking](https://forum.communityhealthtoolkit.org/t/mitigate-duplicate-data-capture/3313) that could be opening the `/add/household` path?

---

_[View the full topic](https://forum.communityhealthtoolkit.org/t/bizarre-recursive-place-case/3825)._