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 API
Created by Guest
Created on Oct 10, 2023

Automatic retry of transaction when a database timeout error occurs

We've noticed some database connection blips that cause errors such as the following exception: "System.Data.Entity.Infrastructure.CommitFailedException: An error was reported while committing a database transaction but it could not be determined whether the transaction succeeded or failed on the database server. See the inner exception and http://go.microsoft.com/fwlink/?LinkId=313468 for more information. ---> System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Operation cancelled by user. ---> System.ComponentModel.Win32Exception: The wait operation timed out"


Upon asking through a support ticket (https://support.optimizely.com/hc/en-us/requests/1231518) we were told this symptoms can be mitigated through a retry of the database operation: "Most of our APIs require that a single "unit of work" (a wrapped entity framework DB context) survive the full duration of that API call. A simple timeout error may be recoverable via code change that re-tries the query"