Empty body_text in flow designer when reprocessing prod-email on non-prod instance

[ChristianF]

I have created an "Inbound Email"-Trigger flow that works as expected/designed. Today the flow created an error and I wanted to analyze the error on our non-prod instance. I exported the email record, imported it on the other instance and reprocessed it, as I have done multiple times in the past. In the first step I call an action with the body_text of the mail as input. This step fails and I can see in the execution details that body_text is apparently empty. When I toggle the scripting on for the input and use body_text of the email it works as expected (fd_data.trigger.inbound_email.body_text).

I do not understand why this flow can't "see" the content of body_text as I have done this procedure 2 weeks ago to test and develop this flow. The same emails I used to test this flow dont work anymore and I havent touched them.

Is there any limitation or reason why body_text is empty when I use it as a data pill and not empty when used in a script?

[Community Alums]

Hi @ChristianF ,

When reprocessing a prod-email on a non-prod instance in ServiceNow, it's possible that the body_text field may appear empty in the flow designer. This can happen if the email content was not properly copied over to the non-prod instance.

To resolve this issue, you may need to manually copy the email content from the prod instance to the non-prod instance. Here are the steps you can follow:

1. Open the email record in the prod instance.
2. Copy the contents of the body_text field.
3. Open the email record in the non-prod instance.
4. Paste the contents into the body_text field.
5. Save the email record.

After following these steps, the email content should now be visible in the flow designer. If you still encounter issues, you may need to review the email processing configuration in both the prod and non-prod instances to ensure they are consistent.

[ChristianF]

Hi Sandeep,

thanks for your quick answer. I dont want to be rude but being this fast and not completly taking all the information into account that I wrote, I highly suspect that this reply is generated by ChatGPT (or other). Also a colleague pasted my question into ChatGPT and got almost the same reply that you gave.