ERR Router uses a non-existent certificate resolver (ecs)

Hi I'm using Traffic with ECS tasks on EC2. I often get errors like "ERR Router uses a non-existent certificate resolver certificateResolver=x routerName=x-http@ecs"

These seem to pop up for all resolvers on a traefik instance whenever a given container is restarted.

Could it be that whenever Traefik detects a new ECS task being started, it's editing the config files to update the list of resolvers, and while the file is locked for writing, reads to it fail because the file is locked?