Expected Pickup-Time translation does not work as expected

Hello there,
we would like to report a technical bug that we found inconjunction with the translation of the expected pickup-time. We were able to narrow down the problem.

!!!The following error only occurs sporadically!!!

#### Issue description

Language changes for the checkout page have no impact depending on the checkout page request return response.
It looks like a split-test to us.

#### Steps to reproduce the issue

Admin Center:

  1. Add Local PickUp store.
  2. Adjust → Information at checkout → Expected pickup time to “Usually ready in 5+ days"
  3. Go to Themes → Edit Languages
  4. Adjust Language for “Checkout & System” → “Pick up in five or more days”

First Variant:

  1. Open a new incognito window.
  2. Put a product to your cart.
  3. Start the checkout process.
  4. Request goes out to ‘/cart’ - Returns a HTTP 302 URL Redirection to 'https://www.emmhpc.com/checkouts/c/{id}’
  5. Redirected Page contains a div tag with the following data-attributes: data-serialized-id=“graphql” && data-serialized-value=“”. The submitted value is a JSON object, which includes
    the right translation.
  6. Fetch/XHR Request goes out to 'https://www.emmhpc.com/checkouts/unstable/graphql’ → Response contains the wrong translation.
  7. Changes have no impact.

Second Variant:

  1. Open a new incognito window.
  2. Put a product to your cart.
  3. Start the checkout process.
  4. Request goes out to ‘/cart’ - Returns a HTTP 302 URL Redirection to 'https://www.emmhpc.com/{id}/checkouts/{id}’
  5. Redirected Page makes a request to 'https://www.emmhpc.com/api/checkouts/{id}/delivery_options.json’ which contains the right information incl. the right translation.
  6. Everything works as expected.

#### What’s the expected result?
Language adjustment should be reflected regardless of the checkout page.

#### What’s the actual result?
Language adjustments are not always working for the checkout page.

Please provide a fix as soon as possible.

Best regards

1 Like

Any resolution to this? We are having the exact same issue.

Any work around to this? I am experiencing the same problem but it’s on my homepage