 So, Shan says, hello all. Quick question on Power Automate Flow. Get items from SharePoint. It's throwing an error. Index was outside the bounds of the array. Gateway timeout. What does this mean? Any help would be appreciated. I read that question, I just think of like robot voice. Index outside the bounds of array, gateway timeout, danger, syntax error, plus prey on tape. So, what does that mean when you get an index error and Power Automate on a SharePoint, get items? It means there's an error, and probably the gateway timeout. Thank you for coming to watch this video. I would probably delete that action, restart Power Automate, and try it again. It's also possible that you're working on a SharePoint list that has an error in and of itself. Really would have to look at the Power Automate. Is this a get item that has triggered from when a new item is created, or is this coming from a Microsoft Forms? What's the trigger? What's happening around it? It's very likely that we're passing some data back and forth that's not happy. Could this be the list threshold limit at 5,000? Is that a possibility? I'm just throwing ideas. That could be. Yeah, because there's returning too many things in the list. It's like, it takes too much time. I can't handle the truth. Yeah, possible. Yeah, try a filter query. Yeah, maybe you're trying to call all the items from the list instead of narrowing it down to a specific view or a specific query maybe. Right, and if it's a get items plural, it might be getting too many items. Trying a filter query so that you only get, even if you say get all items where the ID equals one, you should only get one item and see if that still gives you the error or not. That'd be a good test. I also have learned the new trick of putting a stop in and add different points because I usually build my power automates and then you run them and get errors, you're like, where to die? I was like, where is it breaking? You can put a stop and say, did it work to this point? Then you move the stop and you're like, yeah, it worked to that point and you put another stop and then another stop and I think that's a, for me, that's been helpful. It's how I used to do that in the old SharePoint design. Designer. Absolutely. Yes. Yeah, of course. Yeah, those terminate functions, terminate actions are amazing for that. Yeah. But it looks like from the question that it's specifically get items. Yeah, I'm not a power automates special, but a lot of times when I see that sort of stuff in other things outside of it, it's because you're looking at completely the wrong data. Are you pointing to the right place? When you look at Excel and other areas or macros or things that I'm building, if it gives me areas that are similar because it's not even pointing in the right place. That's a good point too. Cool. It depends. I just like the fact that Jonathan started the whole thing by saying, have you tried turning it off and on again? Absolutely. We always stop there. It's okay, Jonathan. It's amazing how many errors I fix and power automate by exiting and going back in. Yeah. It's some cash in the browser, because it all works in the browser. Exactly. Something could be cash in the browser holding it up, but it may not even be the process. It could be how you're accessing power automate. Or maybe they have bad internet, bad Wi-Fi and the signals dying halfway through the thing that it's doing and it's just giving up. Every time the signal dies at the exact same spot. Yeah. That sounds right. That's where the stop thing helps. Where did it die? How far did it make it? Yeah. The fact that he specifically says get items from SharePoint, it's throwing the error tells me that it's getting to that action every time. Yeah. I would start with a filter query. Try to get one item and see if that works. If it doesn't work, then it's probably not the action itself that's the problem. It's a data. It's a data issue of some sort. Or you might have a weird variable or the dynamic content that you're requesting in it somewhere. This to me comes to a bigger question because SharePoint is fabulous. The lists are fabulous, but they do have limitations. Maybe this isn't the right tool. Maybe this should be built in the Dataverse where you have more robust data management features than what SharePoint lists offer. That would require requirements and architecture and thinking through this and planning and design Sherry. Now, let's not get crazy.