Skip to content
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

Closed
stcz opened this issue Apr 15, 2022 · 3 comments · Fixed by #318
Closed

No Information about failed Jobs on Webpage #313

stcz opened this issue Apr 15, 2022 · 3 comments · Fixed by #318

Comments

@stcz
Copy link
Contributor

stcz commented Apr 15, 2022

I have some failed jobs in my qfield cloud under the jobs tab.
Jobs

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.

@suricactus
Copy link
Collaborator

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".

@stcz
Copy link
Contributor Author

stcz commented Apr 20, 2022

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.
I had no indication when looking for the cause of the failure. For a user, it would be great to see what happens and why the job failed.

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.

@suricactus
Copy link
Collaborator

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?

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants