For some reason, adding certain dependencies to Actions will simply disappear after deployment (whether by Deploy CLI or through the browser UI).
Only some though, such as lodash or uuid, which leads me to think it’s packages already in the dependency graph somewhere? But this is rather opaque behaviour. Can anyone confirm?
I should note that the Action works fine regardless.
As this topic is related to Actions and Rules & Hooks are being deprecated soon in favor of Actions, I’m excited to let you know about our next Ask me Anything session in the Forum on Thursday, January 18 with the Rules, Hooks and Actions team on Rules & Hooks and why Actions matter! Submit your questions in the thread above and our esteemed product experts will provide written answers on January 18. Find out more about Rules & Hooks and why Actions matter! Can’t wait to see you there!
I can confirm, this happens with me.
After deploying the action, the dependency went missing.
and some other times the action steps gets removed from the flow automatically.