# \[Solved\] 400 "Version not allowed"

**URL:** <https://forums.losant.com/t/solved-400-version-not-allowed/553>\
**Category:** Bug Report\
**Created:** [July 18, 2017, 9:54am UTC](https://forums.losant.com/t/solved-400-version-not-allowed/553 "2017-07-18T09:54:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rwild\_node](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@rwild\_node](https://forums.losant.com/u/rwild_node)\
**Post date:** [July 18, 2017, 9:54am UTC](https://forums.losant.com/t/solved-400-version-not-allowed/553/1 "2017-07-18T09:54:32Z")

</div>

I have some workflows that have been running for sometime, I noticed tonight the payload on 2 seperate workflows wasn’t getting sent to the devices and I am getting this error message on the debug:  
 ![](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/1X/484acc567373c571502357d0ce82e1df96f8cc62.png)

It seems to be stemming from the ‘losant-API’ panel in the workflow which is as follows:

 ![](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/1X/36288f802d073873ef57fd6a19ef3be369899224.png)

When i click into the ‘resource and action’ tab it seems to be highlighting the ‘Application -GET’ function as follows:  
 ![](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/1X/20e6451663339c4b2f8e2b1786ea2e934e124c17.png)

I have selected ‘Devices: GET’ again and re saved the workflow but hasn’t seemed to work. Any ideas or something thats changed which is causing this issue? Cheers.

---

<div class="post-metadata">

**Author:** ![Michael\_Kuehl](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/michael_kuehl/32/99_2.png) [@Michael\_Kuehl](https://forums.losant.com/u/Michael_Kuehl)\
**Post date:** [July 18, 2017, 12:10pm UTC](https://forums.losant.com/t/solved-400-version-not-allowed/553/2 "2017-07-18T12:10:57Z")

</div>

Thanks for bringing this to our attention! It looks like we had some issues with a deploy rollout that were not caught by our automated checks (going to be adding this to our automated checks in the future) - the issue should now be fixed and the node should be working properly in all cases again.