You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At some point during the job where we create the subscriptions in Subscribe Pro we lock the order, and update the flags so that the order is not included in the list of subscriptions to be created.
If there is another job running which locks the order you can receive ORMOptimisticLockingException?
When this happens the subscription is already created, and the flag is not cleared. This causes the subscription to be created again in Subscribe Pro.
Expectation
Subscriptions are only created once per order.
Additional thoughts from SFCC Support regarding the job
Thank you for your patience. I trying to read through some of the code for both of the job and I see for PostProcessingExecution, I am seeing below json being taken from customer preference and I see something about Order. Is this job reading orders and adding data to custom object(like you mentioned before or is it doing something else) ?
Also, for job: ProcessSubproSubscriptions-Process, I see that ExecuteScriptModule.Transactional flag is enabled and I believe in the script you have transaction.wrap statements as well. I would suggest to disable the ExecuteScriptModel.Transactional flag (especially when you are processing a lot of orders to process and having this enabled kill the system because it wraps the entire script within a transaction and since script has its own transactions, these will become nested transactions. This should be enabled only for small scripts that do not have transactions within them).
The text was updated successfully, but these errors were encountered:
Issue
Duplicate subscription created in Subscribe Pro
Details
At some point during the job where we create the subscriptions in Subscribe Pro we lock the order, and update the flags so that the order is not included in the list of subscriptions to be created.
If there is another job running which locks the order you can receive
ORMOptimisticLockingException?
When this happens the subscription is already created, and the flag is not cleared. This causes the subscription to be created again in Subscribe Pro.
Expectation
Subscriptions are only created once per order.
Additional thoughts from SFCC Support regarding the job
The text was updated successfully, but these errors were encountered: