action_status field in system user run flow not updating - UTAH

[Ron28]

I have an issue where in an extended Task record, the action_status field is not updated from a Flow Designer flow in an "Update Record" step.

I have an application that from a Catalog Item triggers a Flow that creates the extended Task record.  A second Flow is triggered when this extended Task record is created or udpated (with a specific update) and does what it needs to, but if it has an issue it will set the extended Task record state to "Pending" and action_status to "Needs Attention". This part works fine.

I also have a Maintenance Catalog Item, where I can select one of my extended Task records that has a state of "Pending" and action_status of "Needs attention". From this Catalog Item I can skip processing for that extended Task record by closing it with state of "Closed Incomplete" and action_status cleared ( -- None -- selected in the Update Record step in Flow designer).  Modifying the state works fine, but the action_status is not updated.

These flows and catalog item were created in UTAH. I have an identical set up created in either San Diego or Tokyo where the above works correctly. 

Both old and new set up run flows as System User and the extended Task table has role "snc_internal" which allows table updates.

I see no errors in the flow, nor do I see ACL errors in the node logs.

Would anyone have an idea what to check or why this would not be working for a flow created in UTAH ?

Thanks

Ron

[Ron28 · Accepted solution]

I've fixed it by the Update Record where field action_status was set to "--none--", script the setting with:  return '';

It's still strange though why setting it to "--none--" doesn't work but I'm ok with the solution.

Ron