Prov Conccurency and plugin alias conflict

I work on a project on AWS using Lambda and the plugin alias.

I face a deployment issue when a provisionned concurrency has been setup on a Lambda.

To be more precise, when serverless apply deployment on Cloudformation; it tries to delete the old version on the alias but fails at first because of the provisionning concurrency allocation on the new version, old version is still associated with the targetted alias.

The cloudformation stack succeed in a second time to delete the old version but the serverless deployment ends in failure.

Would be any solution to prevent serverless deployment from failling ?