Problem
The external Post Processing timeout was already increased to 60 seconds, which was a useful improvement. However, a fixed timeout can still be limiting for interactive or more complex workflows where the external process may legitimately need more time before returning the final image.
In these cases, the timeout can interrupt an otherwise valid Post Processing flow.
Suggested solution
Please make the external Post Processing timeout configurable directly in the Post Processing settings.
For example:
60 seconds
120 seconds
300 seconds
Off / No timeout
The current 60 second value could remain the default, so the existing behavior would not change for users who do not need a longer timeout.
The "Off" option would be especially useful for external applications that already provide their own timeout and error handling.
Example use case
We use external Post Processing with our own application.
After LumaBooth starts the application, an interactive selection screen is shown. The user first chooses how the image should be processed and the final image is then returned to LumaBooth.
The actual image processing itself is fast. The variable part is the user interaction before processing. Some users make their selection immediately while others may need more time. During this entire period, LumaBooth’s 60 second Post Processing timeout continues to run. This means a valid workflow can time out simply because the user took longer to make a selection.
Our application already has its own timeout handling, so an unlimited wait on the LumaBooth side would work well for this type of workflow.
Expected behavior
With a configurable timeout, users could choose the value that fits their workflow.
With "No timeout" selected, LumaBooth could continue waiting until:
The processed image is returned
The external process aborts or fails
The operation is manually cancelled
This would make external Post Processing much more flexible while keeping the current 60 second behavior as the default.
If there is already a supported way to extend, bypass or disable the external Post Processing timeout, we would also be very interested in knowing about it.
