caioq opened a new issue, #8198: URL: https://github.com/apache/incubator-devlake/issues/8198
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened The problem occurs during subsequent executions of a blueprint after the initial or full-refresh data collection has been completed successfully. Initially, all data is collected perfectly, and there are no errors or unusual behavior logged during these runs. However, in some cases, during subsequent runs of the same blueprint, old issues seem to be deleted, leaving only issues that were created or updated after the last pipeline execution. ### What do you expect to happen Records should be incrementally added to the `issues` table. ### How to reproduce This started happening 2 weeks ago in the production environment. I don't know if the [JIRA incident on November 5-6](https://jira-software.status.atlassian.com/) may have impacted this collection process. ### Anything else Upon further investigation, I found that the `_raw_jira_api_issues` table still contains 73,145 records, while the `_tool_jira_issues` and `issues` tables only hold 1,115 records. This suggests there might be an issue with the extractor or data transformation during these runs. ### Version v1.0.1-beta8@e195107 or v1.0.2-beta4 ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
