Triggered auto assignment to @mallenexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

@mallenexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Console error bug, not priority, will address and reproduce soon.

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

@mallenexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

Pinged Tomasz to check on summin

Tomasz got back to me and I haven't been able to prioritize this yet

Checking to see if batching console errors for a v2 cleanup might be a good approach

• [HOLD for payment 2024-11-29] Console error cleanup.  #51099 (comment)

From @rinej in a 1:1. Sharing partially as a reminder to myself.

when we receive a 429 error, it usually means the user has sent too many requests within a given time frame. It seems the backend API has a rate limit in place to prevent this.
If this happens frequently, I think it would be best to adjust the rate limit on the server API side

Off the next week then will revisit

Submit and pay expenses on the workspace chat consecutively, at least more than 3 times

This is an edge case, the fact we haven't seen this reported much, if at all, the past 3 years makes me think it's not a bug most users would ever run into, going to close. Comment/reopen if you disagree.