Long running import causes Gateway Time-out (504) error
codescape opened this issue · comments
If the data set is too big the import will run into a Gateway Time-out (504) on the browser side but the import will still continue and finish. This should be changed and the import should be implemented more robustly - for example will a long running task with the current results being reported by the GUI.
Idea: Start the import / scan and ping for the results asynchronously from that page.