Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: pyCommitError on Create, Copy (Save As), or Import of a circumstanced rule

Updated on October 2, 2015

When you try to save some circumstanced rules, you get the pyCommitError. You see the error in any of the following situations:

  • Creating a new circumstance rule
  • Performing a Save As of an existing rule
  • Attempting to import a circumstance rule

Successful creation of circumstance rules depends on the PXINSNAME column of the pr_index_circumstance_def database table having an adequate width for internal tracking of the rules.

A column width of 128 characters or less is inadequate. Increase the PXINSNAME column width to 255 characters or more.


2014-06-18 21:45:16,137 [http-apr-8080-exec-7] [Developer] [pegasupport:01.01.01] (Accel_Optimization_Work.Action) FATAL localhost| pegasupport - .pyCommitError: ** A commit cannot be performed because a deferred save of instance

#20140619T014515.885 GMT!1!CDEF failed: code: <none> SQLState: <none> Message: <none>


For the database table pr_index_circumstance_def, if the PXINSNAME column width is 128 characters or less, you experience this issue. The following screens illustrate one of the scenarios that triggers the error.

Circumstanced rule Section Save As


Suggested approach

If the width of the PXINSNAME column in the pr_index_circumstance_def table is 128 characters or less, increase the column width to 255 characters.

Related content

Circumstances and other rule qualifiers

Circumstances — Concepts and terms

Working with the PegaRULES database Index tables

About Circumstance Definition rules

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us