Aborted query notification in Redshift

I faced a weird behavior of the Redshift cluster (the support ticket is still open with service team: Case ID 9386087231) where COPY command query sent by the LambdaRedshiftLoader getting aborted first, and then re-written, and competed successfully by the Redshift engine. The problem is that the only Aborted result reported back to the Lambda function and batch status marked as 'error'. I verified in the Redshift that data was loaded successfully in this scenario.
Also, the complexity of this issue is that there is multi cluster scenario, where data loaded to two Redshift clusters and only one is failing with the above scenario. This leads to a question I can't find an answer to in this repo: If I reprocess the 'error' batch does the data loaded to both clusters, or solution is smart enough to load failed batches only for failed Redshift clusters?

Inizia con i percorsi di elaborazione batch e retry di LambdaRedshiftLoader, concentrandoti su come vengono riportati i risultati di COPY quando Redshift interrompe e riscrive una query. Riproduci il caso multi-cluster, se possibile, e determina se la rielaborazione di un batch in errore ripete il tentativo su entrambi i cluster o solo su quello non riuscito; l’issue è completa quando sono stati stabiliti tale comportamento e lo stato corretto del batch.

Scritto dal modello di indicizzazione a partire dal testo della issue.