Sometimes getting "Show your HTML text here." when running Flow

[sammybridge]

I am running a Power Apps triggered Flow which creates a HTML document in SharePoint. Most of the times I run it, it works completely fine, but sometimes it is creating the document and none of the HTML text is showing and instead it just says "Show your HTML text here."

Is there any reason it takes multiple attempts at the same action to work?

I have attached screenshots of Flow and Power Apps button.

[JohnAageAnderse]

Hello @sammybridge 

Please verify that your content does get passed from the Power App to the Flow in the flow runs where the issue appeared.

Kindly inform us about the result.

Kind regards, John

[v-litu-msft]

Hi @sammybridge,

Could you please share where the "Show your HTML text here." appear?

Is there any reason it takes multiple attempts at the same action to work?

If the action run successful, means the file create correctly, you could check the Flow run history to check it.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[sammybridge]

Hi @v-litu-msft  @JohnAageAnderse 

Here is an example. I first ran the Flow and got the standard "Show your HTML text here." and then ran it seconds after and it has grabbed the HTML correctly the second time.

[JohnAageAnderse]

Hello @sammybridge 

Thank you for your information. Can you verify in the first flow run that you posted, that the parameter "Createfile_FileContent..." has the content that the Power App sent to the flow?

Suggest to add a Compose action before your Create file action and add the parameter there. Then rerun and check the value in the Compose action.

Kind regards, John

[sammybridge]

Hi @JohnAageAnderse 

Thanks for continuing to come back to me. I have added the compose in and re-run the Flow and I can see that it isn't getting the data from Power Apps properly. 

[sammybridge]

Hi @JohnAageAnderse and @v-litu-msft 

Is there anything else you can suggest to do on this? It looks like the problem isn't carrying over from Power Apps, but I don't understand why it does it sometimes and not others.

Thanks

[JohnAageAnderse]

Hello @sammybridge 

What is the definition, in flow, of the input from PowerApps?

What is the definition, in PowerApps, of the parameter sent to Flow?

Provide as much details as you can, so we may be able to suggest/help 🙂

Kind regards, John

[sammybridge]

Hi @JohnAageAnderse 

So in Power Apps it is triggered on select of a button and the code is being pulled from an HTML label. The label is made up of a series of things including collections, plain text and variables.

I thought initially it would be because it wasn't creating the collections quick enough but then it should still contain the plain text in the HTML and that doesn't work either.

[JohnAageAnderse]

Hello @sammybridge 

Could your code check the content to be sent, so that it will stop with a warning, if the content is just the "Show your HTML text here"? Then test and test till you get the issue and can hopefully identify the steps that lead to it.

Kind regards, John

[johnom]

Anyone got an answer to this?

It's intermittent and can't figure it out

driving me nuts!!!!

[JohnAageAnderse]

Hello @johnom 

Can you show us the actual steps that you have in you flow?

I am curious to why you have a parallel split just after the Power Apps action!

Kind regards, John

[johnomahoney]

Hi

maybe got the wrong john?

My flow has no split - just a straight forward  create, convert and save

[JohnAageAnderse]

Hello @johnomahoney 

I went to far back in this thread 😄

Can you open a run in which the issue appeared, expand all the actions, then take a screenshot of everything! Edit out any data you don't want us to see 🙂

Kind regards, John

[johnomahoney]

ha  - no problem  - they can get very long

here is the flow

HTML is created in Powerapps 

as mentioned it works most of the time

[JohnAageAnderse]

Hello @johnomahoney 

Thank you for the screenshots, but that is from the flow itself. Can you take the screenshots of the flow run where you had the issue? Then we can identify if the issue is in the flow or in the data being delivered to the flow!

Kind regards, John

[johnomahoney]

ok, I have compared 2 flows from the same user on the same day

one creates pdf , one does not

The difference in the code is that on the trigger output the one that fails has

"Connection": "Keep-Alive",

[johnomahoney]

It seems that the 'request in powerapps' in the create file section, is not picking up the html in powerapps all the time. If someone more techy than me could help explain why and how to fix  - that would be awesome!!

[JohnAageAnderse]

Hello @johnomahoney 

To me that looks then to be an issue in the Power Apps! It does not always deliver the data to the Power Automate (flow). Please review the Power Apps functionality.

To allow you to verify that the Power Apps does or does not deliver the data, add a compose action before the Create file PO and add the Power Apps data field in the Compose input field.

Then in the future runs, you can check what was delivered to Power Automate!

Kind regards, John

[johnomahoney]

ok, cheers

I have set up a respond to powerapps for both outcomes with a message to inform the user if the PDF was created

Maybe some helpful info:

when you create an HTML box the default text is 'Show your HTML text here'

This is what is getting passed sometimes to Power automate

So the condition I am checking for is if size = 56 in order to determine what message to send back