# Jobs inconsistently report "Error" although run to completion

**URL:** <https://forum.ansible.com/t/jobs-inconsistently-report-error-although-run-to-completion/37538>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [January 9, 2023, 9:20pm UTC](https://forum.ansible.com/t/jobs-inconsistently-report-error-although-run-to-completion/37538 "2023-01-09T21:20:40Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![Brian\_O\_Neill](https://avatars.discourse-cdn.com/v4/letter/b/d26b3c/32.png) [@Brian\_O\_Neill](https://forum.ansible.com/u/Brian_O_Neill)\
**Post date:** [January 25, 2023, 8:19pm UTC](https://forum.ansible.com/t/jobs-inconsistently-report-error-although-run-to-completion/37538/21 "2023-01-25T20:19:23Z")

</div>

Excellent, I’ll try that next chance I get and I’ve also subscribed to the issue.

---

<div class="post-metadata">

**Author:** ![shrutebattlestargala](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shrutebattlestargala/32/2029_2.png) [@shrutebattlestargala](https://forum.ansible.com/u/shrutebattlestargala)\
**Post date:** [January 25, 2023, 8:34pm UTC](https://forum.ansible.com/t/jobs-inconsistently-report-error-although-run-to-completion/37538/22 "2023-01-25T20:34:22Z")

</div>

Also you can create your own execution environment and specify that ee in your job templates

**novumrgi/awx-ee:stable**

---

<div class="post-metadata">

**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\
**Post date:** [January 25, 2023, 9:50pm UTC](https://forum.ansible.com/t/jobs-inconsistently-report-error-although-run-to-completion/37538/23 "2023-01-25T21:50:26Z")

</div>

doco you may also try running without reconnect support

[https://github.com/ansible/receptor/pull/683](https://github.com/ansible/receptor/pull/683)

see how RECEPTOR\_KUBE\_SUPPORT\_RECONNECT is enabled in the awx spec in that PR? try setting to disabled and see if that helps

Note, with reconnect disabled you may experience other issues, particularly if your jobs runtime exceeds 4 hours

---

<div class="post-metadata">

**Author:** ![shrutebattlestargala](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shrutebattlestargala/32/2029_2.png) [@shrutebattlestargala](https://forum.ansible.com/u/shrutebattlestargala)\
**Post date:** [January 26, 2023, 3:15pm UTC](https://forum.ansible.com/t/jobs-inconsistently-report-error-although-run-to-completion/37538/24 "2023-01-26T15:15:37Z")

</div>

I have a sandbox to use if we still need to run these tests from the ee container - **client rate limiter Wait returned an error: context canceled**

---

<div class="post-metadata">

**Author:** ![Brian\_O\_Neill](https://avatars.discourse-cdn.com/v4/letter/b/d26b3c/32.png) [@Brian\_O\_Neill](https://forum.ansible.com/u/Brian_O_Neill)\
**Post date:** [January 27, 2023, 2:55pm UTC](https://forum.ansible.com/t/jobs-inconsistently-report-error-although-run-to-completion/37538/25 "2023-01-27T14:55:28Z")

</div>

I disabled the reconnect support, and that fixed all my job issues. I don’t have a need to run 4+ hour jobs at this time anyways.

[Previous page](https://forum.ansible.com/t/jobs-inconsistently-report-error-although-run-to-completion/37538.md?page=1)