I’m using the Run Background process plugin and set the timout to 300000 (so 5 minutes). When the process is run in the background it still reaches a limit of 30 s. Does this plugin setting actually work?
Hi Joeri,
The default time-out for a runbackgroundprocess is 1 hour. Thus if you leave the time-out parameter empty the proces will run for a maximum of one hour. Every timeout you configure under a hour should therefor work in my opinion. A time-out above 1 hour will not work automatically because then other web.config time-out needs to be set to a higher value (see below):
Based on your screenshot your configuration seems fine. I stared a lot at your screenshot because 30.000 would explain the 30 seconds 
. But it says 300.000 so nothing wrong there.
The only suggestion I have at this moment is to try and capture the proces using a trace so maybe some more information will be present to see what goes wrong.
It is also possible that you are hitting a different timeout than the background process timeout. For example, there is also a timeout specifically for sql queries, which defaults to 30s.
We’ve actually managed to find a workaround, by setting this appsetting:
This is temporary offcourse, because setting this to 5 minutes is not what we want (for this process it’s temporary, so it’s fine).
@Martijn When I ran the process with the runbackground plugin in it, it still reached the timeout of 30s. Maybe what @Wim said is true. Wim, do you have any suggestions for this? We want it to be configurable in the run background process plugin what the timeout is.
To clarify: The setting you set in the web.config (database.commandtimeout) is the one Wim is talking about.
1 Like