[Bug][Zentao] Sync Error in Zentao Integration: Execution ID 7 Request Fails

[narrowizard]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

When synchronizing data from Zentao using DevLake, an error occurs with the message:

Error running pipeline 302431. Wraps: 
(2) Error running task 444478.1. Wraps: 
(2) Subtask collectExecutions ended unexpectedly. Wraps: 
(3) Retry exceeded 3 times calling /executions/7. The last error was: Http DoAsync error calling [method: GET, path: /executions/7, query: map[limit:[0], page:[1]]. Response: ("error": "error") (400).

Upon investigation:

The execution with ID 7 no longer exists in the target project (verified through the /project/{project_id}/executions API).
However, this ID is still present in the tool table of the database, suggesting it may be stale data.
Attempting to trigger the Blueprint task with fullSync: true also did not resolve the issue.

What do you expect to happen

When triggering synchronization or Blueprint tasks, the system should:

Validate the existence of execution data in the target platform (Zentao).
Ignore or clean up stale data from the database to avoid errors.
Complete the synchronization process without failure.

How to reproduce

1. Set up a DevLake integration with Zentao.
2. Perform the initial data synchronization from Zentao to DevLake.
3. Delete an execution (e.g., execution ID 7) from the Zentao project.
4. Trigger synchronization again in DevLake.
5. Observe the error message: /executions/7 Request Failed.

Anything else

No response

Version

release-v1.0

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[narrowizard]

Ignore the inference above. Upon further investigation, the issue originates from the collectExecutionSummaryDev subtask. This subtask collects a non-existent execution (ID: 7), which causes the collectExecutions request to fail.