Skip to main content
Solved

HTTPCaller in FME Flow unable to parse URL past attribute value

  • November 6, 2025
  • 2 replies
  • 72 views
jelwell93
Contributor
Forum|alt.badge.img+4

I have an FME job which is based on the JobFailureNotify example provided by this article below, where I have an automation that triggers on a job failing and then runs this workspace to email me some details from the JSON it provides.

Send Email Notification on Failed or Cancelled Jobs – FME Support Center

I’m using 2025.1 and apiv4. When I try to test it in FME Flow, I get the following error. It’s like FME Flow cannot handle the URL in the HTTPCaller to have ‘/log’ after an attribute value.

My request URL is: https://<MYSERVERURL>/fmeapiv4/jobs/@Value(jobID)/log (where <MYSERVERURL> is my FME Flow URL).

If I manually type in a job ID, the URL works. It only fails when the job ID is an attribute value. I have tried concatenating the entire URL into a new attribute and using that as the request URL, but that did the same thing. Anyone got any ideas how to get around this? I’ve attached a screenshot of my HTTPCaller as well.

53 2025-11-6 11:53:35 | HTTPCaller (HTTPFactory): HTTP: The URL 'https://<MYSERVERURL>/fmeapiv4/jobs/2378
54

2025-11-6 11:53:35 | /log' could not be parsed

Best answer by aaron.hillier

Hi ​@jelwell93,

I’m sorry to hear you’re experiencing this issue! I quickly ran through that tutorial as well, and I experienced the same error.

 

It seems like there is an issue with how the JSON is being parsed in the workspace. If you inspect the data coming into the HTTPCaller, you will see that the ‘jobID’ attribute has a ‘newline’ at the end, which is why the HTTPCaller is unable to parse the URL, and likely why the error message is being split across two lines. To fix this, I simply added a second StringReplacer that removes this new line from the end of the ‘jobID’ attribute before its used in the HTTPCaller. Another option that worked for me (and involves one less transformer) is to remove the StringReplacers and simply use an AttributeTrimmer, which removes all of the whitespace from the input attribute in one go if you leave the “Trim Characters” parameter blank:

 



I hope that makes sense! Let me know if those options work for you, or if you have other questions. We’ll look into updating that article so that other users don’t experience this same issue.

 

-  Aaron H.

1 Attachments
danilo_fme

2 replies

aaron.hillier
Safer
Forum|alt.badge.img+6
  • aaron.hillierSafer
  • Safer
  • Best Answer
  • November 10, 2025

Hi ​@jelwell93,

I’m sorry to hear you’re experiencing this issue! I quickly ran through that tutorial as well, and I experienced the same error.

 

It seems like there is an issue with how the JSON is being parsed in the workspace. If you inspect the data coming into the HTTPCaller, you will see that the ‘jobID’ attribute has a ‘newline’ at the end, which is why the HTTPCaller is unable to parse the URL, and likely why the error message is being split across two lines. To fix this, I simply added a second StringReplacer that removes this new line from the end of the ‘jobID’ attribute before its used in the HTTPCaller. Another option that worked for me (and involves one less transformer) is to remove the StringReplacers and simply use an AttributeTrimmer, which removes all of the whitespace from the input attribute in one go if you leave the “Trim Characters” parameter blank:

 



I hope that makes sense! Let me know if those options work for you, or if you have other questions. We’ll look into updating that article so that other users don’t experience this same issue.

 

-  Aaron H.

jelwell93
Contributor
Forum|alt.badge.img+4
  • jelwell93Contributor
  • Author
  • Contributor
  • November 11, 2025

Thanks Aaron, the AttributeTrimmer has done the trick!

Community Stats

32,154
Posts
122,043
Replies
39,812
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.