GitHub abuse detection might lead to replacement issues

When creating issues at GitHub, I sometimes get HttpError status 403 with the message ‘You have triggered an abuse detection mechanism and have been temporarily blocked from content creation. Please retry your request again later.’ This error leads to the creation of a replacement issue, as can be seen from the output below:

        ...ERROR while migrating issue #5.
DEBUG:
 { HttpError: You have triggered an abuse detection mechanism and have been temporarily blocked from content creation. Please retry your request again later.
...
}
 -> creating a replacement issue...

I’d expect that in this case the issue would be skipped and/or the program would wait before proceeding and no replacement issue is created. There was basically nothing wrong with the issue itself.