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
The retry logic will attempt to retry a failed db operation.
However, it does not currently preserve the original exception that caused the operation to be retried. The code that walks the exception tree to detect certain errors will then always default to the fail-through exit code of 5, rather than the specific error codes for certain known errors. This ends up having misleading messaging to users about why their jobs failed, and more tech support.
We should probably try an include the original exception in the exception tree, by passing it to the retry logic, and raise the final error from original_exception. This is both technically correct, and the existing code should work with it.
The text was updated successfully, but these errors were encountered:
The retry logic will attempt to retry a failed db operation.
However, it does not currently preserve the original exception that caused the operation to be retried. The code that walks the exception tree to detect certain errors will then always default to the fail-through exit code of 5, rather than the specific error codes for certain known errors. This ends up having misleading messaging to users about why their jobs failed, and more tech support.
We should probably try an include the original exception in the exception tree, by passing it to the retry logic, and raise the final error
from original_exception
. This is both technically correct, and the existing code should work with it.The text was updated successfully, but these errors were encountered: