# Receptor version compatibility **URL:** \ **Category:** Get Help\ **Tags:** awx, ee\ **Created:** [February 20, 2025, 3:26pm UTC](https://forum.ansible.com/t/receptor-version-compatibility/40397 "2025-02-20T15:26:17Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![2and3makes23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/2and3makes23/32/1406_2.png) [@2and3makes23](https://forum.ansible.com/u/2and3makes23)\ **Post date:** [February 20, 2025, 3:26pm UTC](https://forum.ansible.com/t/receptor-version-compatibility/40397/1 "2025-02-20T15:26:17Z")
Hi there, I have a question regarding receptor version compatibility. - In our EE we use receptor:devel (like in [awx/awx-ee](https://github.com/ansible/awx-ee/blob/devel/execution-environment.yml#L69)), which currently points at receptor ~1.5.3 - On our Execution Nodes (RHEL9), OS repos provide receptor 1.4.4 This combination (AWX EE running receptor:devel and Execution Node running receptor:1.4.4) seems to work fine, but is it “supported”/recommended? The EE image is rebuilt nightly so, its receptor version stays up to date. If Execution Nodes are not constantly updated (with non-OS packages) as well there is bound to be some kind of drift. The most careful approach might be, pinning receptor within EE (in contrast to [awx/awx-ee](https://github.com/ansible/awx-ee/blob/devel/execution-environment.yml#L69)) and moving pin forward regularly in sync with execution nodes. What is the recommended strategy to keep everything working well together? ---
**Author:** ![AaronH88](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/aaronh88/32/663_2.png) [@AaronH88](https://forum.ansible.com/u/AaronH88)\ **Post date:** [February 26, 2025, 4:56pm UTC](https://forum.ansible.com/t/receptor-version-compatibility/40397/2 "2025-02-26T16:56:49Z")
While we do our best to ensure backwards compatibility our testing suits only test mesh’s that have a common version, e.g. everything 1.4.4 or everything 1.5.3, Mixing receptor versions is best effort on our part and not “supported” I hope this makes sense. So far we have one receptor version that is not backwards compatible due to a known bug on the internal workunit id, so please avoid v1.5.0. This version was never officially released in AAP so you should only get it if you manually install it. ---
**Author:** ![2and3makes23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/2and3makes23/32/1406_2.png) [@2and3makes23](https://forum.ansible.com/u/2and3makes23)\ **Post date:** [March 6, 2025, 3:25pm UTC](https://forum.ansible.com/t/receptor-version-compatibility/40397/3 "2025-03-06T15:25:03Z")
Thank you very much for clearing that up for me. 🙂 ---
**Author:** ![2and3makes23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/2and3makes23/32/1406_2.png) [@2and3makes23](https://forum.ansible.com/u/2and3makes23)\ **Post date:** [March 24, 2025, 9:03am UTC](https://forum.ansible.com/t/receptor-version-compatibility/40397/4 "2025-03-24T09:03:58Z")
If anyone is interested, what I started doing in regard to receptor on each AWX Update For our custom EE build: - look up and apply ansible.receptor [pin for resp. AWX version](https://github.com/ansible/awx/blob/24.6.1/awx/api/templates/instance_install_bundle/requirements.yml) - Pin receptor version to the latest version released at the time of above collection version On Execution nodes: - Update receptor to same version ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [April 23, 2025, 9:04am UTC](https://forum.ansible.com/t/receptor-version-compatibility/40397/5 "2025-04-23T09:04:13Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.