Redeploying an unchanged DO Declaration results in an intermittent error. This error shows up as a 500 after provisioning AVR on a device that was already deployed. First first dryrun and deployment works. Subsequent deployments after that of an unchanged declaration will occasionally throw the following error either during deployment or during dryrun:
"tryUntil: max tries reached: missing required field",
"Cannot read property 'process' of undefined"
Steps To Reproduce
Steps to reproduce the behavior:
Submit the following declaration (some values redacted):
Environment
Summary
Redeploying an unchanged DO Declaration results in an intermittent error. This error shows up as a 500 after provisioning AVR on a device that was already deployed. First first dryrun and deployment works. Subsequent deployments after that of an unchanged declaration will occasionally throw the following error either during deployment or during dryrun:
Steps To Reproduce
Steps to reproduce the behavior:
Submit the following declaration (some values redacted):
Observe the following error response:
Expected Behavior
I would expect a declaration that was successfully deployed would not error out on the second run when the values in the declaration have not changed.
Actual Behavior
The declaration will error out with a 500 and the error of "cannot read property 'process' of undefined"