Skip to content

[Due for payment 2026-09-28] [Onyx] Investigate UnknownError: Attempt to generate key in database without an in-progress transaction storage error #100046

Closed

Description

@fabioh8010

Parent issue: #87844.

Coming from #87844 (comment).

Sentry issue: https://expensify.sentry.io/issues/APP-KG

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. sosek108 commented on Sep 1, 2026

    @sosek108
    Contributor

    This exact log line does not come from Onyx. This is combination of WebKit (100% of occurances are from WebKit) flavour of IndexedDB and 3rd party libs (such as gib.js).

    Sometimes (usually after long inactivity or refresh) WebKit kills database's connection and every read/write that were in flight fails with errors like Attempt to get a record from database without an in-progress transaction..

    Attempt to generate key in database without an in-progress transaction is a variant of our log lines that are most probably caused by described WK behaviour. It does not come from Onyx, because Onyx does not use any kind of API that raises this error. This is noise related to 3rd party scripts and does not affect user at all.

    The potential problem that came up while investigating with Claude
    The same WebKit behaviour can occur while the application is booting up. Onyx tries to load local data, gets the error, and gives up. The error line that could occur is Attempt to get records from database without an in-progress transaction.

    Simple solution is to mark these errors as TRANSIENT in our error classification (instead of UNKNOWN). Onyx will reconnect to database.
    This is not solution to APP-KG. APP-KG is not related to onyx and should be because it's not related to our codebase and does not any harm to user

  2. fabioh8010 commented on Sep 2, 2026

    @fabioh8010
    ContributorAuthor

    @Julesssss what do you think?

  3. Julesssss commented on Sep 3, 2026

    @Julesssss
    Contributor

    Great, sounds reasonable to me. And if I understand the PR correctly it's already done?

  4. fabioh8010 commented on Sep 3, 2026

    @fabioh8010
    ContributorAuthor

    Yeah Onyx PR was merged, @sosek108 could you do bump to 3.0.110? 3.0.109 hit production already.

  5. sosek108 commented on Sep 3, 2026

    @sosek108
    Contributor

    @fabioh8010 @Julesssss Yes, I'll handle this!

  6. sosek108 commented on Sep 4, 2026

    @sosek108
    Contributor

    Bump PR here: #100385

  7. melvin-bot commented on Sep 8, 2026

    @melvin-bot

    Triggered auto assignment to @pecanoro, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  8. added and removed
    ReviewingHas a PR in review
    on Sep 9, 2026
  9. 7 remaining items

  10. sosek108 commented on Sep 17, 2026

    @sosek108
    Contributor

    @pecanoro do you think this issue can be closed / resolved? There was on PR reviewed here

  11. pecanoro commented on Sep 21, 2026

    @pecanoro
    Contributor

    Ah yes, closing!

  12. DylanDylann commented on Sep 28, 2026

    @DylanDylann
    Contributor

    @pecanoro Could you reopen this issue to handle the payment for my review of #100385?

  13. changed the title [-][Onyx] Investigate `UnknownError: Attempt to generate key in database without an in-progress transaction` storage error[/-] [+][Due for payment 2026-09-28] [Onyx] Investigate `UnknownError: Attempt to generate key in database without an in-progress transaction` storage error[/+] on Sep 28, 2026
  14. melvin-bot commented on Sep 28, 2026

    @melvin-bot

    Current assignee @mallenexpensify is eligible for the Awaiting Payment assigner, not assigning anyone new.

  15. pecanoro commented on Sep 28, 2026

    @pecanoro
    Contributor

    @mallenexpensify, can we issue a payment to @DylanDylann for reviewing the PR?

  16. melvin-bot commented on Sep 28, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  17. mallenexpensify commented on Sep 28, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @DylanDylann due $125 via NewDot

    $125 cuz tests weren't needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions