terraform rate limit prevents apply but tf shows complete

Issue with running outside of gihub actions from within our github.com/ibm/automation* repos... when you run and hit a rate limit error, the module seems like it will just move on to the next module. terraform will complete successfully, but the module with the rate limit never gets installed / created in the repo. The problem I'm seeing is that you can not just re run terraform apply and get that module to re-run and apply because terraform already sees it as applied it never gets touched. and you are forced then into a destroy/manual cleanup / re run scenario which is really messy.