Hi Community,
This is my last attempt to get some help with power automate the "low-code" / "no-code" solution... Not being a developer but willing to learn new things, I tried following many examples and videos etc. to simply Create a MS Form, take the output of the form to populate a word template file on SharePoint and store the resultant document to SharePoint Online... The creation of the form was relatively straight forward, the creation of the Word Template was also all good, then I had to learn about site columns and site content types in SharePoint in order to pass the dynamic values from Forms through Power Automate to the Template file...
All went great until I noticed because of field limitations in SharePoint (i.e. Single line = 255 characters), I needed to change some of the column definitions to multi-line. The I found out if you have a date value for a field or a numeric value for a field and bypass it in the flow (through a branching operation) the data passed (i.e. "NULL") would fail the flow, so then we go about dealing with potential NULLS in the flow (flow is growing exponentially now...) just to deal NULLS in these fields... then we go on to learn about dealing nonnumeric data passed from Flow to power automate because we didn't set a restriction on the form field to only accept a numeric value, no sooner we get that sorted we start to hit the next set of challenges, specifically where flow passes, yet run fails and then when checking the flow output I see the following....
Simple retrieve the information from the form and if NULL set it to blank through the ' ' at the end of the coalesce expression (don't ask why coalesce, been around the block with expressions now including the replace(replace... , json( ) defined ones and coalesce seemed to be the one not returning errors like "input expects a string, you passed a null, or input expects an array you passed a string, etc. etc.

I put break points in the flow to literally check each step before moving on to next definition or running the flow in its entirety, when satisfied I get no errors I run flow and then start seeing things like this...

yet when expanded the below cryptic message appearing

In fact, just about every compose field showing this type of error (here I was thinking compose is just an arbitrary placeholder to display "data in motion", nevertheless the flow finally fails at the Update file properties section with a similar message to the one displayed on the compose action...

and then I notice the message at the top of the screen saying I hit a threshold....

all of this just because I wanted to get rid of strange characters like " [ \ | etc. being presented with multi-select options in my MS form....
Can anyone point me in the right direction to finding out what this error actually means and why it occurs? I have even gone so far as downloading Visual Studio 2022 hoping to connect to the data to see where and why it is failing but that is presenting other challenges like SharePoint foundation not installed, what would be great if there was somewhere (a site or something) or even if MS showed you in the flow or presented an error code in the flow to give you a hint where to look for the problem.... telling me it can't fetch something is not helpful if you don't tell me why, being an old IT type guy, I see "443" as part of the error message and I assume that there is something wrong with the credentials or SSL layer, but my connections are fine, I authenticate on the connectors to both SharePoint and Forms, the PC I'm using is sitting as registered in the Azure AD so where to now????
The two other posts I made on this forum Re: Query regarding Apply to each "loop" to remove... - Power Platform Community (microsoft.com) and Re: Dealing with NULL's in Power Automate using co... - Power Platform Community (microsoft.com) show a lot more detail of the flow in its various rewrite iterations, if that might be useful, but I got past those errors and now this is the latest...
PS: I don't want to use the Premium Power Automate word template connector as Mick Hucknall from Simply Red once said "Money's too tight to mention..."