I am trying to start a job on FME Flow from another application by making use of a webhook and a token. The trigger results in succesfully starting a job on FME Flow, but the response is most of the time the following:
1502 - Web server received an invalid response while acting as a gateway or proxy server.
It looks like this only happens when the job takes longer than 2 minutes. Does anyone have an idea where the 502 response comes from? This indicates an error while in fact the job is started as expected.
Version 2022.2
Build 22765 - win64
Best answer by hkingsbury
stefan.vdbergwrote:
Thanks for your response @hkingsbury. You are correct, we are using a reverse proxy (IIS) and it indeed looks like a timeout there, because the call waits for the job to succeed or fail. I will try to split the call into submitting the job and retrieving the result.
as you're using IIS i'm therefore assuming you're using ARR - it could be as simple as increasing the timeout in ARR.
But yes, for longer running jobs, it generally is a good Idea to follow a more async style process and submit a request (and retrieve the job id) then poll the job ID until you no longer get a processing state
Did this help you find an answer to your question?
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.
Thanks for your response @hkingsbury. You are correct, we are using a reverse proxy (IIS) and it indeed looks like a timeout there, because the call waits for the job to succeed or fail. I will try to split the call into submitting the job and retrieving the result.
Thanks for your response @hkingsbury. You are correct, we are using a reverse proxy (IIS) and it indeed looks like a timeout there, because the call waits for the job to succeed or fail. I will try to split the call into submitting the job and retrieving the result.
as you're using IIS i'm therefore assuming you're using ARR - it could be as simple as increasing the timeout in ARR.
But yes, for longer running jobs, it generally is a good Idea to follow a more async style process and submit a request (and retrieve the job id) then poll the job ID until you no longer get a processing state
as you're using IIS i'm therefore assuming you're using ARR - it could be as simple as increasing the timeout in ARR.
But yes, for longer running jobs, it generally is a good Idea to follow a more async style process and submit a request (and retrieve the job id) then poll the job ID until you no longer get a processing state
Agree. Thanks for your help :)
Hi FME community,
I am trying to start a job on FME Flow from another application by making use of a webhook and a token. The trigger results in succesfully starting a job on FME Flow, but the response is most of the time the following:
1502 - Web server received an invalid response while acting as a gateway or proxy server.
It looks like this only happens when the job takes longer than 2 minutes. Does anyone have an idea where the 502 response comes from? This indicates an error while in fact the job is started as expected.
Version 2022.2
Build 22765 - win64
Page 1 / 1
My first thought is that you're reaching a connection timeout somewhere along the line.
Are you connecting to Flow through a reverse proxy or similar?
Thanks for your response @hkingsbury. You are correct, we are using a reverse proxy (IIS) and it indeed looks like a timeout there, because the call waits for the job to succeed or fail. I will try to split the call into submitting the job and retrieving the result.
stefan.vdbergwrote:
Thanks for your response @hkingsbury. You are correct, we are using a reverse proxy (IIS) and it indeed looks like a timeout there, because the call waits for the job to succeed or fail. I will try to split the call into submitting the job and retrieving the result.
as you're using IIS i'm therefore assuming you're using ARR - it could be as simple as increasing the timeout in ARR.
But yes, for longer running jobs, it generally is a good Idea to follow a more async style process and submit a request (and retrieve the job id) then poll the job ID until you no longer get a processing state
hkingsburywrote:
as you're using IIS i'm therefore assuming you're using ARR - it could be as simple as increasing the timeout in ARR.
But yes, for longer running jobs, it generally is a good Idea to follow a more async style process and submit a request (and retrieve the job id) then poll the job ID until you no longer get a processing state
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
