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

cannot run `oms:check-condition` with parameters, it works just fine without them, but once I run `o

2»

Comments

  • Thomas Lehner
    Thomas Lehner Support Engineer @ Spryker Posts: 289 🏛 - Council (mod)

    @U01G4K5E0J2 thanks, can you also please tell me the business impact and when this will be a blocker for you? This will help me prioritize the case correctly

  • U01G4K5E0J2
    U01G4K5E0J2 Posts: 194 🧑🏻‍🚀 - Cadet

    well, pretty high,
    if I understand correctly,
    • oms:check-conditions doesn't create OMS lock, like oms:check-timeouts does,
    • oms:check-conditions takes orders disregarding from what store they came, APP_STORE is used only for stuff like currency, locale etc.
    and since we wanted to have multiple cronjobs for this, one per store, only way to achieve this in a secure way was running oms:check-conditions --storeName=AT|DE|EN|etc,
    this bug seems to make this approach impossible

  • U01G4K5E0J2
    U01G4K5E0J2 Posts: 194 🧑🏻‍🚀 - Cadet

    currently we disabled this cronjob for all stores except one

  • U01G4K5E0J2
    U01G4K5E0J2 Posts: 194 🧑🏻‍🚀 - Cadet

    but at some point we would like to have one job per store

Categories