Dynamic Flow action within sub-Flow does not save certain pills from earlier sub-Flow steps<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } User Steve Stevens had a sub-Flow with a Dynamic Flow action on step 5. When Steve tried to drag and drop data pills into certain fields in the Dynamic Flow action, they would drop successfully. However, on saving the sub-Flow and then re-opening the Dynamic Flow action step after, the pills were not actually being saved. This was due to the Dynamic Flow action step being corrupt. The fix was to remove the Dynamic Flow action step, save the sub-Flow, and re-add the Dynamic Flow action step, reassociating all data pills. Then, on saving, all data pills selected remained.