A small preview of what I’ve been working on since this morning: a clean display of errors in the « background tasks » view! 
I’ve always been against displaying raw logs in the UI (because we know what that leads to, then we get lazy and do integrations where we ask people to look for IDs in the logs 
), but I’m in favor of a view like this, where:
- All known errors are translated, and the steps to follow are clearly explained for the user. Example here with a simple error: Gladys restarted while a task was running: this is normal behavior, and it should be specified.
- For unknown errors, we display it as-is so the user can give us feedback, then two options:
- It’s a bug, we fix the bug
- It’s an error that can occur under certain conditions (not a bug): Example « OUT_OF_MEMORY »/« DISK FULL », etc… In this case, we add this error to the list of translated errors, with a clear message, and with steps to resolve the error.
Here’s what the view looks like for now:
What do you think?