Hi @NatBlendCo 

Good question.

It would seem that a required field is either not set correctly as a static value/selection or not dynamically mapped correctly between the Zap steps.

Hey @NatBlendCo if you are still having trouble with your Zap, would you be able to post screenshots so we could work through this with you? 

Hi @NatBlendCo, thanks for sharing your screenshots with us. 

In your screenshot, in the lifecycle_stage_name field, you can see that instead of having the stage, it has a number and the name of a field in double brackets. When you see that in the data out of your Zap history, that means that the field that you had put into the Lifecycle stage field no longer exists. 

This is usually something that you can fix pretty quickly, let’s walk through it! To start with go to your Zap and open a new draft. Before you do anything else, re-test your Zap’s trigger, this makes sure that you’re working with the most up to date version of your trigger data. Then ,go to the step with the lifecycle field. Delete the field that is currently in the lifecycle box and re-add the relevant field from your new trigger data. Finally, re-test your action to makes sure that it’s working the way that you want to. 

I hope that gets things running smoothly again, let us know if you need some more help!