Skip to content

Commit 36a2e37

Browse files
authored
Update HighPaymentsRequestsLatency.rst
1 parent 280c153 commit 36a2e37

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/how-it-works/HighPaymentsRequestsLatency.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ Troubleshooting steps
77
----------------------
88

99
1. Check the pods the alert is fired on for errors
10-
2. Check that the `supabase` pod on the cluster is up and running properly. It's used to store and get payment requests.
11-
If the `supabase` db is unhealthy, this is probably the cause for it. For this, contact the DB INFRA team
10+
2. Check that the `postgres` pod on the cluster is up and running properly. It's used to store and get payment requests.
11+
If the `postgres` db is unhealthy, this is probably the cause for it. For this, contact the DB INFRA team
1212
3. Check account-config workload. It's also used on the payment requests flow. For errors in this workload, contact the `config management` application team
1313

1414
If any of the above has error, this is most likely the issue

0 commit comments

Comments
 (0)