Confirmations required always shows as 1

[SanLeo461]

Just gonna paste in what I posted in the safe-wallet-monorepo issue:

Bug description

Transactions once signed & proposed by one user show as needing only 1 confirmation total and ready to be executed, while the true threshold is 4.
This is with regards to the safe at: https://nova.arbiscan.io/address/0x2C0BDb957F5a6976E4Ceb5A34470bFB13D30a278

If this is some bizarre indexing issue and you know where to override it for a temporary fix, that's good enough for me, however I couldn't find where the threshold was stored in any of the DBs.

Environment

• Production
• Browser: Chrome, on Windows & Linux
• Wallet: MetaMask
• Chain: Arbitrum Nova (42170)

Steps to reproduce

1. Go to [Link redacted]

Expected result

Threshold shows as 4

Obtained result

Threshold shows as one and appears ready for execution

Screenshots

[on-waterfall]

I have the same bug.
I discovered that SafeStatus is not created in the database.
If I manually add it to the database, it works.

[SanLeo461]

I have the same bug. I discovered that SafeStatus is not created in the database. If I manually add it to the database, it works.

Worked for me, thanks!
Took ages to figure out the syntax and get the data inserted though haha.

I'm gonna leave this open in case the team wants to investigate further on the issue or ask any questions of me, otherwise maintainers feel free to close.
Cheers

[on-waterfall]

But this is not a solution to add manually, it should be added automatically

[SanLeo461]

But this is not a solution to add manually, it should be added automatically

Yeah it should be definitely, in my case though I only needed a one time fix. I'll leave this up and hopefully the safe team can fix it properly.

[on-waterfall]

I add processing to WORKER_QUEUES env and it works

WORKER_QUEUES=default,indexing,processing