Article ID: 116609, created on Aug 1, 2013, last review on Mar 31, 2016

  • Applies to:
  • Plesk for Linux/Unix


A customer or Provider on customer's behalf cannot place upgrade/downgrade order for a subscription in PBA Control Panel due to the error message saying that conflicting order exists:

Cannot Upgrade/Downgrade Resources for Subscription #1000101: there is already an Upgrade/Downgrade Order #UG000101 in status New(NW). This order prohibits placing an order of the Same Order Type (Per Subscription). Please either cancel conflicting order or wait while it will be processed or contact Provider.

Setting the status mentioned in an error to not prevent other orders placement (Prohibit Order Placing to Don't Prohibit in the order flow) does not make any changes.


PBA has a built-in mechanism which prevents provisioning of conflicting orders, e.g. PBA does not allow to provision upgrade/downgrade order if another non-completed upgrade/downgrade order exists because it is not always clear what amount of resource must be set for a subscription by two non-completed orders, how to bill the customer correctly.

The setting Prohibit Order Placing does not play any role in this case by-design, the check is implemented internally. This information is mentioned in the documentation.

Also, it is not possible to renew subscription if it already has non-completed renewal order.


PBA provides order number of the conflicting upgrade/downgrade order. A customer or Provider may find the order in PBA Control Panel and either cancel it or complete the order provisioning. After the conflict is resolved the customer can place new upgrade/downgrade order for their subscription.

Search Words

conflicting order

order failure



198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 614fd0b754f34d5efe9627f2057b8642 29d1e90fd304f01e6420fbe60f66f838

Email subscription for changes to this article
Save as PDF