You’re offline. This is a read only version of the page.
14
Hi Everyone,
I have a simple share point flow. There are 2 lists. The "style list" has a style number column which should have a unique number. ( enforced unique values) . The second list is "style_color" list which gets the style number from "style list" by a lookup.
We have some additional columns in "style list" which we get these fields by a "get item" action in a flow. Flow looks like below.
I had also added a trigger condition to avoid loops. If the value of trigger column is Yes then the flow runs and after this run it changes the trigger column to No. So this is like a manual trigger.
This flow worked perfectly in last 1,5 years. But recently the flow is failing as below.
Because I can not see and select the get item list id in the dynamic content. Now all our operations are stopped as the flow does not work. I have a case with microsoft about this problem but no improvement in last 3 weeks. Flow team sent me to share point team but no progress so far.I could not talk with anybody in microsoft support team who knows both sharepoint and flows 😞 It looks like this is a bug or something is corrupted as the flow has been working perfectly in last 1,5 years and we did not change anything. Now it does not work. Did anyone have such a problem ? Can you help me ?
Thank you !!!
Deniz Ozgentas
Hi,
Thank you for your reply. I added title value in one of the raws and tried to run the flow but it still fails in the update item action after performing all necesseary actions there. As you said my field name in STYLE_COLOR list is TRIGGER in the list settings as below.
However when I select it from dynamic content it shows as TRIGGER_YES_NO ?? Also existing flow which triggers with condition works with below condition which is TRIGGER_YES_NO
@equals(triggerBody()?['TRIGGER_YES_NO'],True)
I guess field name is supposed to be be same but it is triggering ??? maybe there is a corruption with the list ?
My actual flow is a very long one with many conditions and actions. It would take long time to create the same but of course it is possible as I have been working on this problem in last 5 weeks ! Also I tried to create a new flow from scretch. you can see below. The trigger condition is same as above.
The flow does not trigger. it says there is a problem with the trigger of this flow
and report shows as below in failed checks
It looks like I am not able to create the flow from scretch 😞 on the other hand STYLE_COLOR list has about 1000 raws and there is another list that gets the items ( same way with GET ITEM ) from STYLE_COLOR list. this list has about 1500 raws. So I have to fix this and use the existing STYLE_COLOR list data. do you think Microsft engineers can fix this ? Their flow team said this is related with the list. sharepoint team said there is nothing wrong with the list. now they passed me to flow team again but i am not sure if this is a flow problem as all the problem is related with STYLE_COLOR list. My other flows ( same structure, pretty basic) about other lists works fine.
All our activities are almost stopped as we depend on these lists and flows and this is really frustrating as microsoft is very slow to take action on these. The support staff do not know details of the subject. They could not make analysis anywere close to you have done so far ! thanks !
thanks for your suggestions !
I don't really see anything wrong, but I did notice that you haven't filled in the Title field and that its no longer displaying as a required field. I would recommend not making those kinds of changes to system level settings. They can often have unexpected side effects. Other than that I don't have any other suggestions on what may be wrong with the flow. It appears pretty straight forward. But given the confusion and unexpected changes to the trigger condition column name I would suspect it has something to do with changes that have been made to the underlying list. You may have to remove and re-add some of the actions to clear up any corrupted metadata. Or worst case scenario start over with a new flow.
Hi,
please see the structure of the update item in the flow. id is the list ID of the triggerbody list ID which is STYLE_COLOR list.
Actually now this update action is performing perfectly as before and completed all the actions. But flow does not go to next step
I got below error message
Hi,
Thank you for your reply. I just checked the field name used in trigger condition and in the TriggerBody dynamic content. You are right! For some reason the filed name in dynamic content is TRIGGER_YES_NO so i added this field name in trigger condition as below and the trigger condition worked. ( I do not know how it was changed to TRIGGER_YES_NO ?? )
Now i can trigger the flow with condition without having a loop. It gets the values from STYLE list. But it fails in next update item action as below. So flow does not perform the other steps.
it says BAD REQUEST STATUS 400
thank you !
Your original screenshot says the field for the trigger condition is ['TRIGGER_x0002e_']. That is not the field name you used in the Compose. Are you sure the field is just TRIGGER? Not TRIGGER_x0002e_ or TRIGGER_Yes_No which I see in the error message?
For the Update Item when the trigger condition isn't in place what field are you using for the ID? Would you provide a screenshot of the Update Item action?
Hi,
Thank you for your reply.
Actually the the code in compose is same as the condition in the trigger. The screenshot does not show the Beginning part of the code. it is below
@equals(triggerBody()?['TRIGGER'],True)
The trigger of the flow is "when an item is created or modified" in the list. Now I removed above condition from the flow trigger, It triggers as below. It gets all the get item columns from STYLE list. But Fails at update item ( meaning can not go to other steps ?) .
On the other hand the flow without above additional trigger condition is not usable as it gets into a infinite loop and stops at the end.
My total number of lookup columns is 10 and below MS max 12 limit! MS support teams can not solve this too.
I spend 2 weeks with flow team and they passed me to sharepoint teams and after addtional 2 weeks they passed me to flow team again. This is very slow and frustrating process!!!
This is very dissapointing when you move all your company date to sharepoint and using the flows and MS could not solve this problem in last 4 weeks !!
thank you for your help.
The code you put in the Compose isn't the same as what you had in the Trigger condition. Also, if you have a substantial number of Lookups you should be using a view to limit the number of columns being returned by the trigger. To answer your question of why it breaks now after running for over a year, there are two options. One, someone may have made a change to the underlying list. For example adding an additional Lookup column. Or Two, MS is continually refining the connectors to improve performance. It may be that one of those changes broke the way you were using the list.
If you removed the Trigger condition and still got an error then the flow did run and the problem wasn't with the Trigger. In the flow run itself what action is throwing the error?
Hi,
I just removed the trigger condition and tried to run the flow. It did not work. Same error. Failed check
I also tried to add a compose action right after trigger
added below condition in expessionstab
@equals(triggerBody()?['TRIGGER'],True)
But it says expresion is not valid. ? I guess i am doning something wrong ? do you mean the above ?
In the meantime microsoft team is working on the related sharepoint list and they asked me to reduce total number of lookup columns to 10. It did not help either 😞
i do not understand why a flow working for 1,5 years without a problem and not working now even we did not change anything in the list structure or flow details ?
thanks
#1
WarrenBelz
146,645
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,997
Most Valuable Professional
Share
Report
All responses (
Answers (
