Skip to Content (Press Enter)
Back to Ideas
36
Like
Follow Idea
Configurable Service Action Timeout
2502Views
12Comments
On our RadarOn our Radar
Backend

When calling a service action, the platform seem to internally set a fixed 100 seconds timeout on the request, so if the action takes longer then that, a "time out" exception is raised on the "Client side" but the action will keep running on the "server side".


I'm not sure if i'm missing a setting here, but in case i'm not, my suggestion would be to either raise the 100 seconds timeout or make it configurable when calling service actions.

24 Apr 2019
Copy link to comment

More than 100 seconds would practically be too long for the user to wait for a response.

24 Apr 2019
Copy link to comment

I'm consuming my service action asynchronously in a timer, so there is no user waiting.


I want to take advantage of the week dependency of a Service Action, but because of the fixed time out, i'm obligated to expose a regular REST and consume it on the other eSpace, that been the only way that i can properly set a time out.


I think that you gotta be very optimistic to believe that ALL Service Actions ever implemented will always last less then 100 seconds.


Also, the exception is only hapening at the consuming side. So the action will be executed until the end but the consumer will be unaware of that. ( the old Atomicity property ).

25 Apr 2019
Copy link to comment

Correct, in this case it makes sense.


Service Actions can have an optional property which could be set for this reason.

25 Apr 2019
Copy link to comment
Changed the category to
Backend
10 May 2019
Copy link to comment

Useful.

18 Jun 2019
Copy link to comment
Changed the status to
On our RadarOn our radar

Hi Matheus,

Thanks for the feedback.

You are correct the timeout is currently hardcoded at 100 seconds, which we were expecting that was more than enough in the most common cases, ideally you don't want to have a service hanged for a long period of time.

Nevertheless we do understand that allowing this timeout to be configured would provide extra flexibility to our customers particular use cases.

We will be looking into adding this setting.

Thanks,

19 Jun 2019
Copy link to comment

One of our applications just got bitten by this same use case - timer consuming service action.

We can adjust the timer logic of course, but it would be really useful to have a configurable timeout.

23 Sep 2019
Copy link to comment

Editable "timeout" is a plus (as applicable for server actions or queries). For those use cases where you won't be able to stick to a "process in small chunks" aproach or your chunks (sometimes) take a bit longer than 100 seconds, it's a waste not being able to use Service Actions.

07 Apr 2021
Copy link to comment

Hi, is there any information about when the timeout setting can be configured for service actions?

25 Jun 2021
Copy link to comment

Hello, same question over here. Has this meanwhile been picked up allowing the timeout that is by default hardcoded at 100 sec to be configured?


23 Jan 2023
Copy link to comment

Hi All, 

We would like to share our experience with regards service actions , our applications got timeout because response time is more that 100 seconds.

So we have to convert all service actions to Server actions but its not recommended as we lost loosely coupled architecture.

Thanks & Regards

Ashish Akolkar

24 Nov 2023
Copy link to comment

It becomes even worse because in Service Studio it is possible to set a custom timeout that will not work for Service Actions:

24 May 2024
Copy link to comment