I’m currently troubleshooting a problem with a SQL-based ETL running on Redshift with SQL Runner 0.5.2.
With the help of AWS Support, I found that it appears the SQL Runner playbook is being run twice; once when it’s kicked off by our cron-based shell script, and then again a few hours later. The SQL files conflict with each other, causing unpredictable results.
I’ve just upgraded to version 0.6.0 and enabled lockfiles to see if that resolves the issue
Has anyone seen this behaviour before?