You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could you open a separate issue if you want to discuss design for storing backtraces? I'm open but curious (both about the use case, and also about what a usable implementation would be)
The job should be preserved if it's in error state, even if preserve_job_records is set to true.
Also can we include call stack for last error inside the job
The text was updated successfully, but these errors were encountered: