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?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.