On our current project, we've been experiencing the following issue when exposing a property. Any actions on the current web node "picks up" the change (meaning the new column is populated when saving a record), however any queue processors/jobs that run on our util nodes do not populate the new column when saving a record.
We can resolve by restarting the utility nodes, however this is a PegaCloud customer so it involves a ticket, coordiation, and delay.
Is there any way (API call, work around, etc.) that will force a node to recognize the new table schema?
We are on 8.4.3.
***Edited by Moderator Marissa to update Platform Capability tags****