Open katelashkevich opened 2 years ago
Same with the reduced variant of this log (reduced means that I deleted all the additional columns so that only the min required data was left) (see "repairExample trimmed.csv"). Uploaded at 15:10 Sept 13, at 16:28 the analysis was still in progress (according to the spinning loader). At 16:28, I intentionally stopped the loading.
When you uploaded the first time the host was down. Any further tries with the same or a similar log right now will produce the same error. (uploaded files are the same so we return the previous result.) @iharsuvorau Could you clear the memory of the server again :) We should maybe look into making a slight change so that when an error was produced by the log for any reason, and the user the log again the execution is tried again and not immediately redirected to the error result
Hi @JonasBerx. Sure, I've just removed all the results. Here's the request for that: DELETE http://193.40.11.233/jobs
. So, anybody can call it (for now).
Agree, in case of an error, make sense to retry instead of returning cached results. I'll make a ticket.
Just a reminder: The documentation for the backend service API is here, http://193.40.11.233/api/.
PS to all: I haven't looked into any of the issues yet. Probably, coming back to them in October after finishing Simod tasks.
Hi, I've just tried to upload two different logs (18:39 Loan Origination (2).csv, 18:44 repairExample trimmed.csv), but again the dashboard did not load. So, the issue remains, I believe.
Uploaded the event log "repair Example (1).csv" at 12:58 13 Sept. The log had all the required data and additional columns that I mapped as "Other." Two hours later, at 15:00, the loading of the dashboard had not finished. For all that time, the upload screen showed that the analysis was in progress (see the screenshot). At 15:01, I intentionally interrupted the loading.
repairExample (1).csv