Skip to main content

#Lightning Lounge #Lightning Flow I have created a flow that will add chatter members to a group based on several requirements being met.  It is a scheduled flow that runs each night at 11pm.  When I use the debug function in flow it works as designed.  When I set the schedule on the start element it fails when the scheduled time arrives.  I setup a debug log and it is failing on my get members lookup element.  Previous to this element, I did a lookup to get the chatter group id.  Here is the debug log.  13:00:07.22 (322819317)|FLOW_BULK_ELEMENT_BEGIN|FlowRecordLookup|Get_Chatter_Group_Members 13:00:07.22 (323319346)|FLOW_VALUE_ASSIGNMENT|78751630de3221f329495bbf57dd170e93ec101-2fad|Get_Chatter_Group_Members|false 13:00:07.22 (323472077)|FLOW_ELEMENT_ERROR|The flow failed to access the value for Get_TimeTrade_Chatter_Group_ID.Id because it hasn't been set or assigned.|FlowRecordLookup|Get_Chatter_Group_Members 13:00:07.22 (323853103)|FLOW_BULK_ELEMENT_END|FlowRecordLookup|Get_Chatter_Group_Members|0|0 13:00:07.22 (756500148)|FLOW_VALUE_ASSIGNMENT|78751630de3221f329495bbf57dd170e93ec101-2fad|error.errorId|3837369-29918 (1594250451) 13:00:07.22 (756532794)|FLOW_VALUE_ASSIGNMENT|78751630de3221f329495bbf57dd170e93ec101-2fad|error.type|FLOW_INTERVIEW_HANDLED_ERROR 13:00:07.22 (756546821)|FLOW_VALUE_ASSIGNMENT|78751630de3221f329495bbf57dd170e93ec101-2fad|error.message|This error occurred when the flow tried to look up records: The flow failed to access the value for Get_TimeTrade_Chatter_Group_ID.Id because it hasn't been set or assigned.

 

The weird part is, the value Get_TimeTrade_Chatter_Group_ID.Id value is not the value in the Get Records Element.  I manually assigned this value.

댓글 7개
  1. 2020년 3월 19일 오후 5:49
    @Tim Peng and @Alex Edelstein I'm not sure if the automated user has access to lookup chatter groups or chatter group members without hard coding the chatter group id as a text variable and setting the default value to the actual id. I did this and the flow worked like I wanted it to. The flow works for now with this workaround, but I'm not a fan of hard coding ID's.
0/9000