Error: Data could not be saved. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding - when adding a revenue category to a payment application

When a payment is created, it can be split among multiple applications, each with its own designation, revenue category, campaign, etc.  However, when a payment has several dozen applications, edits to the payment or application may hang or time out, returning the message:

Error: Data could not be saved. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.

We are currently evaluating this issue and will update this article when we have more information.
Workaround: Make changes to the applications using a revenue update batch instead of through the payment.

Environment

 2.9.1001, patch 95 ; 2.94.1524

Was this article helpful?