I have an API endpoint in "API Server" linked to .morph file
Morph file workflow contained "Web Request" action which can take up to 6 mins to completed.
When calling API endpoint from external application, after extacly 5 mins, the workflow stopped. I check the journal log in "Endpoint", the status is "Workflow canceled by user".
I suspected this is due to the time out of API endpoint. Do we have option to increase this timeout from 5 mins to 7 mins.
Hi, @Quang_Nguyen
Could you please share a screenshot of the journal entry where the workflow fails, with the Errors tab open? This would help us investigate the issue further.
Hello @Quang_Nguyen regarding the "Web Location" connector that is being used in your "Web Request" action, what is the specified request timeout? If you can include a screenshot like the one below of your connector, that would be great. Thanks!
Hi, this is the journal log:
Hi, Roberto
I increased the connector time out to 10 mins already but still failed after 5 mins when running workflow through API endpoint call. I tested the connector in Easy Morph client and it run perfectly (not failed after 5 mins).
My guess is workflow (.morph file) triggered by "Task" has options to change the time out or no time out, but workflow running through API endpoint don't have that option and may be having default time out = 5 mins.
Hi @Quang_Nguyen thanks for the screenshots.
Can you also include a screenshot of the "Status Log"? In your first screenshot, where it says "Status log (33)".
I have run projects through the API Server that lasted 7 minutes and they finished successfully. Let's see if there's something specific about this project that is causing this cancellation.
Can you also indicate which version of Hub (Server) you currently have?
Thanks
Hi @roberto ,
Nothing special, just query to SQL database & some "Web Request" action using "Web Location" connector (already set very high timeout).
The version of Server is 5.9.8
Hi @Quang_Nguyen thanks for the information.
Can you scroll down to the last status logs that do not appear in your screenshot, and send them over as well?
Thanks
Hello @Quang_Nguyen
Could you please try running the same .morph project as a Task on the same server and in the same Space where the API endpoint is configured?
If the Task is also cancelled, please enable Diagnostic log in the Task settings, run it again, and send us the resulting diagnostic log.
This will help us determine whether the cancellation is related to the project execution itself or to a specific API endpoint.
Thanks
