Stripe

Delayed
FinanceAPI keyEvery 15 minutes
Explore data
Running lateRATE_LIMITED
Stripe is rate-limiting Kimo

Another integration on your Stripe account is consuming most of the read quota. Kimo backs off automatically, so data is about 3 hours behind instead of 15 minutes.

How to fix: Lower the sync frequency of other Stripe apps, or switch Kimo to Stripe’s event webhooks for near-real-time updates.

Rows synced
0
Tables
5 / 5
Last sync
3 h ago
Avg. run duration
21s
Success rate · 30d
0%

Rows synced per day

Last 30 days · all tables

5,926
avg 198/day

Freshness

Target: under 45m

3h 0m
behind source · 3 h ago
Delayed
0SLA 45m
Next syncin 15 min
Lag, last 7 dayshover a cell
Sat
Sun
Mon
Tue
Wed
Thu
Fri
LowHigh

Sync runs

Last 14 runs · every 15 minutes

  1. PartialOct 9, 11:29 · Scheduled
    13s24 rows
    HTTP 429 — rate limit reached, 3 h behind
  2. SucceededOct 9, 11:14 · Scheduled
    18s47 rows
  3. SucceededOct 9, 10:59 · Scheduled
    19s24 rows
  4. SucceededOct 9, 10:44 · Scheduled
    12s50 rows
  5. SucceededOct 9, 10:28 · Manual
    1m86 rows
  6. SucceededOct 9, 10:14 · Scheduled
    18s20 rows
  7. SucceededOct 9, 09:59 · Scheduled
    17s51 rows
  8. SucceededOct 9, 09:44 · Scheduled
    13s27 rows
  9. SucceededOct 9, 09:29 · Scheduled
    17s31 rows
  10. SucceededOct 9, 09:14 · Scheduled
    22s52 rows
  11. SucceededOct 9, 08:59 · Scheduled
    24s51 rows
  12. SucceededOct 9, 08:44 · Scheduled
    21s54 rows
  13. SucceededOct 9, 08:29 · Scheduled
    17s49 rows
  14. SucceededOct 9, 08:14 · Scheduled
    13s23 rows

Volume by table

Top 6 of 6 tables · rows

Used by

2 data models