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
{{ message }}
Repository navigation
Improve retryOperation and reportStorageQuota logging to include original error #87780
OnyxUtils.retryOperation and OnyxUtils.reportStorageQuota can log messages that omit the original storage error. This forces investigators to search nearby logs by timestamp to find the actual failure.
Update logging in both functions to always include the original error in every log path, making it directly queryable in Sentry and VictoriaLogs.
changed the title [-]Improve retryOperation and reportStorageQuota logging to include original error[/-][+][Due for payment 2026-05-15] Improve retryOperation and reportStorageQuota logging to include original error[/+]on May 8, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.68-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
changed the title [-][Due for payment 2026-05-15] Improve retryOperation and reportStorageQuota logging to include original error[/-][+]Improve retryOperation and reportStorageQuota logging to include original error[/+]on May 12, 2026
Activity
MrMuzyk commentedon Apr 15, 2026
I am Michał from Callstack - expert contributor group. I’d like to work on this job.
MrMuzyk commentedon Apr 17, 2026
Will take a while to release this, bump is now 3.0.61 and this changes are in 3.0.68
MrMuzyk commentedon Apr 29, 2026
Preparing Bump PR
MrMuzyk commentedon May 7, 2026
Bump on staging
[-]Improve retryOperation and reportStorageQuota logging to include original error[/-][+][Due for payment 2026-05-15] Improve retryOperation and reportStorageQuota logging to include original error[/+]melvin-bot commentedon May 8, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 8, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.68-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-05-15. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 11, 2026
@fabioh8010 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
[-][Due for payment 2026-05-15] Improve retryOperation and reportStorageQuota logging to include original error[/-][+]Improve retryOperation and reportStorageQuota logging to include original error[/+]Julesssss commentedon May 12, 2026
Payment handled in the sibling issue: #74470