Menu
Feedback
Start here


Known issues
SLA offer fluctuating between different shipping policies due to cache in estimated date of 30 seconds
ID: 1036916
Backlog
Published on 5/21/2024
Last update on 5/21/2024

Summary

The logistics simulation can oscillate between offering SLAs if the client has shipping policies with the same price, delivery time, SlaType, dock cost and warehouse configuration, but different dock priority. We have a cache that stores the delivery time for 30 seconds, so when a new simulation is made, another shipping policy with the same configurations that has a longer dock time may be offered when it shouldn't be.

Simulation

Shipping policies A and B with the same total delivery time (1 day for example), price, dock cost and warehouse, but with different dock priorities. Make a quote at 16:00:00 where shipping policy A with lower dock priority will be offered, then the estimate result would be for the next day at 16:01:00, this data is cached for 30 seconds; When making a new quote at 16:00:10 for example, shipping policy B with a higher dock priority will be offered, because in the first quote the delivery time would be for example at 16:01:00 cached for 30 seconds, while the second quote B is chosen because it also has the estimate for the next day but at 16:00:00.

Workaround

There is no workaround for a scenario with the same settings as described above.

Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX community.
Join our community
Request support from VTEX
For personalized assistance, contact our experts.
Open a support ticket
GithubDeveloper portalCommunityFeedback