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..

Hi, does someone noticed those errors too and does someone know how this error can happen?

UK7KBE2JW
UK7KBE2JW Posts: 463 🧑🏻‍🚀 - Cadet

Hi, does someone noticed those errors too and does someone know how this error can happen?

Comments

  • This type of errors appear when you try to trigger event (OMS) for order item before previous one was not finished yet or timeout was not exceeded.

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

    ok, thank you. so it could be possible that if we have an timeout event that throw orders into invalid state after some time passed and the state was not changed since the task did not run again because it is still running, so that we are missing some orders even they are valid?

  • I don’t understand your question clearly. What exactly do you mean “miss order”? Order was not exported to your external system through some OMS command?

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

    correct. some order where move to invalid after some time even the order was payed and valid

  • You can manage those type of case via OMS by moving orders from invalid state back to step before export

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

    yeah i know, but we wanna prevent those failures so no manual tasks are not necessary