-
-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Information about failed Jobs on Webpage #313
Comments
The reason why there are no logs available is that... well, no logs were available for these jobs. There is not much that can be done, probably we can just add "no logs available". |
Thank you for this answer. On my point of view, it looks like the outage from 16. April was caused because the deltas were not applied by the corresponding service that is doing this. Has the System the ability to receive even more details as "no logs available"? For Example, "Job could not start because of a Server Error" or anything else that could happen? For a user it would be great to determine if the error is caused by the server, that i can open a ticket, or the error is caused by me, and i have to act by myself. |
This is what I meant. Until this is implemented, you can safely assume there was a server error if the logs are missing. If the error is caused by the user, it would be shown in the logs. |
I have some failed jobs in my qfield cloud under the jobs tab.
On succeeded jobs I'm able to click on the Job ID to receive more details.
On failed jobs I'm not able to click on the Job ID, and so I'm not able to receive details what went wrong.
To investigate the cause, it would be great to receive more details about the failures.
Thanks for your work.
The text was updated successfully, but these errors were encountered: