ODC version
4.3.2
OB version
no related
What happened?
When a logic database changes a task, the task should end and release resources after the execution fails
What did you expect to happen?
After a task fails to run and is the last set of SQL statements to be changed, the task should be terminated and should not occupy resources
How can we reproduce it (as minimally and precisely as possible)?
Initiate a database change ticket, and observe the running status of the ticket
Anything else we need to know?
No response
ODC version
4.3.2
OB version
no related
What happened?
When a logic database changes a task, the task should end and release resources after the execution fails
What did you expect to happen?
After a task fails to run and is the last set of SQL statements to be changed, the task should be terminated and should not occupy resources
How can we reproduce it (as minimally and precisely as possible)?
Initiate a database change ticket, and observe the running status of the ticket
Anything else we need to know?
No response