Skip to main content

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.

Support Article

Unable to save data into exposed columns on some nodes



Unable to save work object data to exposed columns on some nodes despite optimized properties.

Error Messages

Not Applicable

Steps to Reproduce

  1. Add columns manually to a table directly in the database.
  2. Create properties with the same name as the new columns.
  3. Save the objects without restarting the instance.

Root Cause

A software use or operation error.

Some application nodes were not restarted after the database schema was changed.


Here’s the explanation for the reported behavior:

As Pega only reads database schema metadata during engine start up, when changes are made to the schema, all instances connected to the database must be restarted.


Published March 18, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us