Savable Data page error handling and save strategy in Constellation Pega v25

General
, ,
1

when a database save is triggered as part of savable data page shape used in a flow, with local save not selected, when does Pega persist the record in the table? Is it when the flow is ending then only data is committed?

I want to have a error handling to check whether actually data is saved, if yes resolve the case else retry. I can do a lookup check immediately after the save datapage shape, but if Pega does not persist the record immediately, the lookup will fail even though in reality save was successful.
is there a OOTB way to know if the save succeeded?

2

In your scenario, I believe Pega automatically commits when an assignment is created or completed, or when the flow ends. A deferred save is therefore persisted at the next applicable commit boundary, which can occur before the flow ends. To confirm the timing in your specific flow, i would suggest to test different scenarios and query the target table using pgAdmin 4 or the Query Runner in Infinity Studio to see exactly when the data gets persisted to DB.