During a deployment with a manual intervention step failed when the admin aborted the deployment. The admin had to then cancel the deployment after realizing the abort did not work. I have attached the deployment process and deployment logs.
cs-charges-process.json (44.5 KB)
ServerTasks-38687.log.txt (28.9 KB)
Hi @ncase ,
Thanks for getting in touch.
Looking at your deployment process, the SQL - Backup Database - Log Backup Production step has it’s run condition set to Always. This is why it ran even though your admin aborted the manual intervention.
I hope that helps.
Thank you and best regards,
Henrik
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.