on some occasions, i am planning to deploy a fixlet / task, and when i hit “OK” and enter my password, i get a reply that the action could not be completed because another administrator is propogating an action.
i am then forced to retry my action several times, waiting a few minutes between each attempt, which is both time consuming and frustrating.
i would like an option that at this point, i will have the option to queue my action, and when the database is no longer locked my action will be executed.
Different users can propagate actions at the same time without any conflicts, but there is a different between normal operators and master operators:
For regular operators – different operators can propagate simultaneously with no proble, but if you are using the same username, you can only propagate one at a time.
For master operators – every master operator propagates to the same actionsite so if another master operator is propagating, you will need to wait for them to complete (even if you have different usernames).
So I am guessing that you are running into propagation conflicts because you have multiple master operators? If so, it is generally a best practice to limit the number of master operators and if it was reasonable in your environment, I would suggest you look at making some of the master operators normal operators, which would eliminate this issue.
Additionally, I am surprised that you run into this problem often… In most systems, you should be able to propagate an action in 30 seconds or so, and it is usually rare someone else would also try to propagate in this time period. How long does it take for you to propagate?