# Validate Payload Node - Schema Invalid

**URL:** <https://forums.losant.com/t/validate-payload-node-schema-invalid/2900>\
**Category:** Help\
**Tags:** workflow\
**Created:** [May 4, 2020, 1:10am UTC](https://forums.losant.com/t/validate-payload-node-schema-invalid/2900 "2020-05-04T01:10:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vander\_Maziero](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/vander_maziero/32/3428_2.png) [@Vander\_Maziero](https://forums.losant.com/u/Vander_Maziero)\
**Post date:** [May 4, 2020, 1:10am UTC](https://forums.losant.com/t/validate-payload-node-schema-invalid/2900/1 "2020-05-04T01:10:40Z")

</div>

Hi,  
The Validate Payload Node is returning “Schema is Invalid” when using the `required` definition, as in the example in [Docs](https://docs.losant.com/workflows/logic/validate-payload/), was any JSON Schema definition changed in the last release? Because a few months ago I saved workflows with this definition, and now it’s not possible because it returns an error.

 ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/b/bb6c87cd0d69f32aee794f73b8831609504404dc.png)

---

<div class="post-metadata">

**Author:** ![anaptfox](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/anaptfox/32/873_2.png) [@anaptfox](https://forums.losant.com/u/anaptfox)\
**Post date:** [May 4, 2020, 1:32pm UTC](https://forums.losant.com/t/validate-payload-node-schema-invalid/2900/3 "2020-05-04T13:32:25Z")

</div>

@Vander_Maziero,

Thanks for letting us know! Our engineering team is on it. I’ll let you know when this is working again.

---

<div class="post-metadata">

**Author:** ![anaptfox](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/anaptfox/32/873_2.png) [@anaptfox](https://forums.losant.com/u/anaptfox)\
**Post date:** [May 4, 2020, 4:44pm UTC](https://forums.losant.com/t/validate-payload-node-schema-invalid/2900/6 "2020-05-04T16:44:46Z")

</div>

Hey @Vander_Maziero,

Thanks for your patience. We have just pushed out a fix for this. I’m happy to answer any questions.
