I seem to be hitting the

autorest/azure: Service returned an error. Status=<nil> Code="AnotherOperationInProgress" Message="Another operation on this or dependent resource is in progress. ... "

issue almost every time I recreate a stack - it's resolved simply by running pulumi up again, but isn't this sortof what pulumi could do for us? That message really means "try again later" - shouldn't there be some inbuilt retry with basic backoff to handle that?