Output Helpful Database Errors to UI (faster debug)

[patricktyndall]

When trying to debug a failing job and it hangs, it's impossible to debug from this tool.

Opening the docker worker logs allows you to see the actual error coming from DB. In my case, data was violating a constraint. Meanwhile, the UI just continues to count up as if it's in progress.

Discovering the source of this error after 10+ minutes of letting the job finish is frustrating.

[nickzelei]

Logs are surfaced in Neosync, but are not available out of the box with the open source version of the tool.
If using an enterprise license or the cloud version, the logs are surfaced directly in the runs page.

FWIW, we also recently updated neosync to fail faster for many more error types. Perhaps this would help you as we were seeing a lot of this as well. Neosync used to fail hard on any error, but that wasn't good and we introduced a whitelist of errors to critically fail on. It might be time to reverse that and go back to hard failing in an error event as the main errors we want to retry we've introduced other more graceful means of failing.