A service catalog flow with multiple stages may cause the history of the RITM to contain duplicate entries for Date fields - Known Error

A service catalog flow with multiple stages may cause the history of the RITM to contain duplicate entries for Date fields Description Updates to a re-used GlideRecord object cause multiple updates to appear in the activity stream.

Steps to Reproduce

1. Add a new column to sc_req_item "date_test" of type Date. 2. Create a flow with service catalog trigger like that in the screenshot. update date_test, then change the stage several times. 3. Associated the flow with a sc_cat_item and "try it" 4. open the sc_req_item and open history > list. 5. observe that the date_test column is listed as changing multiple times when it had only be set once. (see screenshot)

Workaround Adding a "Wait for duration" flow logic of 1 second before changing stages in your flow will avoid the duplicate history entries.

This works because it will quiesce the flow and force a fresh glide record to be used when the stage is updated.