Search Engine: Elastic

Article ID: 131380, created on Aug 30, 2017, last review on Aug 30, 2017

  • Applies to:
  • Business Automation 7.0
  • Business Automation 7.1


Order status is Completed but Provisioning Item status is Failed.

Order was completed however Order item was still in failed state.


There can be several different reasons for such behaviour:

  1. bug #PBA-79497 ("Order is completed but order item is failed"), reseller's balance is checked once again
  2. Incorrect events order processing, e.g.:

    • order placed, submitted, failed, "Create Service" event failed
    • order resubmitted, new event "Create Service" placed and processed -> OItem got status "Completed"
    • cancellation order is placed and processed right away, subscription destroyed
    • the first "Create Service" was resubmitted (as its number of attempts not yet exceeded) and failed due to substriction already destroyed -> OItem got status "Failed"

    The issue is corrected in scope of #PBA-79678 ("Billing Task Manager performance improvements"). In scope of that request task manager was redesigned and in that version new "Create Service" event would not be placed, an old one would be processed instead. As a result, the possibility to get incorrect status is avoided.

  3. Some manual actions can cause the described situation


In case subscription is already destroyed, no worakround is to be applied, incorrect OItem status does not influence any billing behaviour. In other cases it may be needed to trigger "Creation Completed" event, each specific case is to be checked.

7c0b495571a6c1bec50e4f324a20ec14 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 198398b282069eaf2d94a6af87dcb3ff b2c3b33425dfc50c7d41a2efaa7f84f3 c0f836394088a28cc30dd0e5fe8b600e

Email subscription for changes to this article
Save as PDF