Skip to main content
Solved

FME Server/Flow HTTPCaller Fails with Web Connection but works on Desktop/Form

  • March 4, 2025
  • 5 replies
  • 155 views

michaelh
Contributor
Forum|alt.badge.img+1

Hi! I could use a hand. 

I'm running an FME workspace that downloads data from ArcGIS Online using 4 HTTPCallers and a Web Connection. The workflow works fine in FME Form 2024, but when I publish and run it in FME Flow 2024.1, it fails.

Setup:

  • Using a Web Connection to authenticate (ArcGIS Online).
  • The Web Connection exists in FME Server and is assigned to my user.
  • The Web Connection is correctly assigned in FME Server.

Does anyone have experience with this issue? Could it be related to permissions, token handling, or FME Server settings?

Any suggestions would be greatly appreciated!

Best answer by bjarne

Try:

1. Re-autenticate the web connection.

2. Publish the workspace to fme flow and upload the web connection. 

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

5 replies

nielsgerrits
VIP
Forum|alt.badge.img+60
  • 2940 replies
  • March 4, 2025

Anything in the log on server? Warnings or errors.


bjarne
Contributor
Forum|alt.badge.img+5
  • Contributor
  • 34 replies
  • Best Answer
  • March 4, 2025

Try:

1. Re-autenticate the web connection.

2. Publish the workspace to fme flow and upload the web connection. 


michaelh
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • 2 replies
  • March 5, 2025

Anything in the log on server? Warnings or errors.

Thank you, ​@nielsgerrits. We are seeing the error in the attached. As one might expect, the URL, group name, and token information follow the error in this screen shot. We are giving your solutions a go as we speak ​@bjarne . 


michaelh
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • 2 replies
  • March 14, 2025

Thank you both! Re-authemticating the web connection did the trick. 


bjarne
Contributor
Forum|alt.badge.img+5
  • Contributor
  • 34 replies
  • March 14, 2025