Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.


We are pleased to announce that beginning on Tuesday, March 25th, we are launching a new feedback experience for our customers!

The new experience should transition over seamlessly, but please be aware that short interruptions to our feedback portal may occur on March 25th between 2:30-4:30pm EDT.


All the best, your Optimizely Product Team

Categories Integration
Created by Guest
Created on Mar 29, 2022

Ability of configuring additional wait time between each job steps

Currently there is no provision in OOTB "SXe 07: Order History" sync-up job to let the job finish its first step( i.e. "Order Header") completely at database level before processing the next step( i.e. "Order Lines").


As we observed that OOTB job is throwing below error frequently while processing the "Order Lines" step because the first step of importing order header has not yet completed at database level .
"Unable to find parent object for mapping field 'ErpOrderNumber' to 'OrderHistory'. Natural key(s): 806946-09 ".

Providing the ability of configuring additional wait time between each job steps (such as a job parameter) will help ensure the step to finish at database level before starting the next one.