What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hey guys, I have a question according to the OMS. When we do versioning for the oms and deploy the n

UK7KBE2JW
UK7KBE2JW Posts: 463 🧑🏻‍🚀 - Cadet
in Help

Hey guys, I have a question according to the OMS. When we do versioning for the oms and deploy the new version, what happens to the old one? Could it be possible that the timeout und condition check for the old versions stops and the process wont run automatically forward?

Comments

  • Andriy Netseplyayev
    Andriy Netseplyayev Domain Lead Solution Architecture Sprykee Posts: 519 🧑🏻‍🚀 - Cadet

    Hey Julian, whenever order is submitted, a respective (current) OMS process (version is included) is picked and saved with the order info. This process will process the order until the very end. All new orders will be processed by the new version

  • Andriy Netseplyayev
    Andriy Netseplyayev Domain Lead Solution Architecture Sprykee Posts: 519 🧑🏻‍🚀 - Cadet

    So you will have them both running in parallel. Once all the orders of the old process are done, it will be safe to remove it.

  • UKEP86J66
    UKEP86J66 Posts: 208 🧑🏻‍🚀 - Cadet

    👍 To ensure the old version orders are processed you need to keep them in the $config[OmsConstants::ACTIVE_PROCESSES] array

  • UK7KBE2JW
    UK7KBE2JW Posts: 463 🧑🏻‍🚀 - Cadet

    Ok, ty. This might be the problem that we dropped them from $config[OmsConstants::ACTIVE_PROCESSES]

Categories