Wiki tab of contents4/15/2023 If you find that misleading, you can change the value to anything you want, as long as you change your loop to track that same value. After that, no matter which one of the errors we’ve received, we set “404” to the StatusCode variable, because that’s the value that allows us to keep on looping. Whenever we receive one of the expected error codes (404, 429 or 502), we stop to wait for 10 seconds. Regardless, we can solve the problem by trying the request again after a little while. Sometimes the response contains the correct “throttled” status code (429, Too Many Requests), but sometimes the status gets returned as 502, Bad Gateway. It is most likely because of the enormous increase in Teams usage in general. Lately, throttling has been happening very frequently with Teams related operations. We should wait a moment before attempting to fetch them again.Īnother reason for the retry logic is throttling. If the response contains status code 404 Not Found, it means the team or the channels are not yet ready. Otherwise, the flow will end due to the error response. Note that it is important that you configure the next action ( Set variable – Response status code) to also get executed if the HTTP action fails. In this case, that is possible by deleting the wiki tab as a part of a Teams provisioning process. As a developer, I always try to think if we can avoid potential issues entirely through automation. Use the OneNote tab instead of the Wiki tab! But that relies on people’s ability to remember to do the right thing. There’s always the option of training users to do things in a certain way. “We keep putting Wiki tabs on all of your Teams channels so you can live on the edge knowing that wiping your entire knowledgebase is just two clicks away!” If the Wiki tab is readded to the channel, the channel wiki starts again from blank. However, instead of ending up in the SharePoint recycle bin, the Wiki content gets deleted permanently on the spot, and there’s no way of recovering it. When the Wiki tab is removed from a channel, the information in that library is automatically deleted. The information written in the Wiki gets stored in a hidden SharePoint library called Teams Wiki Data on the team site connected to the team ( Wiki Data). I don’t know who has originally thought it to be a good idea, because using the Wiki tab can easily lead to a permanent loss of information. Whenever you create a new channel for a team, a Wiki tab is automatically added to the channel.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |