encodeUriComponent for List Folder / Problems with shared documents in Share Point (The response is not in a JSON format.)

[ArtHavenShelter]

Hi, I have a great working flow but PowerAutomate gives me weekly messages that they have to turn off the flow because of the failed status. I read something today about the EncodeUri component but just don't know what to do. I got help before from @KvB1. See the topic link below.  The problem is at the List Folder part. There the flow gives an error message "The response is not in a JSON format." I don't know what to do to create the proper EncodeUri parameter given the File Identifier Variables. Please advise, help and solve this with me. 
Kind regards, 
Art, The Haven Night Shelter Cape Town

Solved: Re: Store attachment, Create folder and check if i... - Power Platform Community (microsoft....

[Expiscornovus]

Hi @ArtHavenShelter,

Looking at the setup in the previous thread and the screenshot over here I would suggest to implement it in your variables (like Shelter).

Below is an example of that approach:

encodeUriComponent(variables('SplitSubject')[1])

[ArtHavenShelter]

Hi, thanks for assisting me in this. Unfortunately it still doesn't work. I still get the same message. It does save the file in the correct folder but the issue remains. Is it possible to do something with 

encodeUriComponent in the List folder part? Kind regards!

[ArtHavenShelter]

Can it be that in the URL of the Sharedfolder is a space in the variable of Client Name? So, not only in the variable itself but also in the input. For example:
the address is: shared%20documents/shelter/Van Helden_CLIENTID_ 

[Expiscornovus]

Hi @ArtHavenShelter,

Yes, that part probably also needs to be encoded (Van%20Helden). Can you test that example?

[ArtHavenShelter · Accepted solution]

Hi,

With the suggestions you made I started to try various things and came with the following solution in the List Folder: 

%2FShared%20Documents%2FsSHELTER%2CLIENTNAME_CLIENTID

Apparently the issue was more for the Shared Documents part. It's not a beautiful solution but it works very well. So I manually Encoded the URL. 

%20 for Space

%2F for /

Nothing more! Result: No Failing issues anymore.