Hi Innes,
There is a Session timeout property that you can change to get around this issue.
- Open /prestohub/config.js
- Change: PRESTO_REQUEST_TIMEOUT: 25000 to say 60000 (milliseconds)
- Save the file.
- Remove browser cache and refresh browser.
This property is not public and is not part of the documentation. However, we will look at better ways of dealing with the timeout issue from PrestoHub in a future release.
- Kishore



Hi mashers,
I've had a quick browse in the 3.0 documentation, but can't find any way to configure the mashup execution timeout period in Presto Hub for a mashup when launched directly.
I've built a mashup that has <parallel> <invoke>'s with long timeout periods set but if you launch the mashup from Presto Hub, the execution times out on the primary mashup well before the <invoke> timeout periods have been reached.
Cheers, Innes