Unable to validate against production as part of Deploy to organization

I am attempting to validate my project against a production org. However, since checking "Validate only" unchecks the "Rollback on error" setting which is required for production validation, I am unable to do so as I get an "INVALID_OPERATION: rollbackOnError option must be true on a production org"

Is this working as designed or am I missing something?

Hi Justin,

Thank you for bringing this issue to our attention.

Our developers will check the mechanism of managing the deployment options and they will solve the issue you are faced with.

I'll keep you updated on the progress of solving this issue, however, may I please contact you later to clarify some more details if this will be needed?

Thank you,

Kate

Sure thing, thanks for the quick response Kate.

Justin

I've also discovered this issue. It gets really annoying if you just try to validate, since deploying with Welkin suppsoed to be much faster than crating a change set, but with this issue, I have to start all over the deploy process. It really eats up time, since I have to reenter all my credentials for the production org.

Hi Laszlo,

Thank you for your post.

May I please ask you to tell me which metadata type files you are deploying when you are faced with the current issue? Also, can you please tell me which actions do you select for your files when you deploy them (Add/Overwrite/Delete)?

Our developers will solve this issue in one of the nearest versions of The Welkin Suite.

Thank you,

Kate

Noticed this issue as well.

In my deployment I am adding 3 new classes and updating 4 classes and 1 trigger.

Definitely of note that this only occurs when selecting the "Validate only" checkbox on the final deployment page. When you're brought to that page, the "Rollback on error" checkbox is checked (though it is greyed out). When I check the Validate only box, it unchecks the Rollback on error box (though still greyed out). Hovering over the Rollback box says "This option is not available for production deployment". I can't tell if this is something specific to my org.

Hi guys,

We have included the work on solving this issue into the next release that should happen in two weeks. I will update the topic once it will be available for you.

Thank you once more for bringing this issue to our attention.

Best regards,

Kate

Thank you Kate, great to hear!