Bettergrow Order bot Refreshed

Settings

How often master data is pulled from ERPNext

ERPNext calls

Every request this system sent to ERPNext. Fewer is better.

7
Today, so far
29
Last 7 days · 4 a day
ERPNext calls by purpose
Purpose Today 7 days Share of 7-day calls
Item master sync 1 5
Customer master sync 1 4
Price list sync (snapshot mode) 0 0
Live price lookups 5 20
Sales Order push 0 0
Push lookups 0 0
Invoice history pull 0 0
Other 0 0

Items

3293 items · item names, codes and units

Daily at 02:00
How often

1–28, so it runs every month

Runs only when someone presses Sync now.

Last sync
2026-10-04 02:00 (unchanged, 1 call, 0 changes)
Next scheduled run
2026-10-05 02:00 — up to date
Records
3293
Last error
—
Last full pull
2026-10-01 03:06
Changes seen up to
2026-09-30 12:09:01.898538 (ERPNext time)
Records in ERPNext
3435 (including disabled)
Sync now fetches changes since the last sync. Full re-sync reloads every record.

Customers

2958 customers · customer names and codes

Daily at 02:15
How often

1–28, so it runs every month

Runs only when someone presses Sync now.

Last sync
2026-10-04 02:15 (unchanged, 1 call, 0 changes)
Next scheduled run
2026-10-05 02:15 — up to date
Records
2958
Last error
—
Last full pull
2026-10-01 03:06
Changes seen up to
2026-09-30 09:26:44.558185 (ERPNext time)
Records in ERPNext
3215 (including disabled)
Sync now fetches changes since the last sync. Full re-sync reloads every record.

Prices

item prices from the Standard Selling price list (snapshot mode only)

Inactive while prices are live
Mode

Live looks up prices in ERPNext for every order (one call per line). A snapshot copies all prices on a schedule and needs the Item Price read permission.

How often

1–28, so it runs every month

Runs only when someone presses Sync now.

Last sync
never
Next scheduled run
inactive; prices are fetched live per order
Records
no data on disk yet
Last error
—
Sync now fetches changes since the last sync. Full re-sync reloads every record.

Working hours

Syncs set to "only outside working hours" wait until this window ends.

A run that fails is retried outside working hours, first 5 minutes later and then at doubling intervals up to 6 hours, until it succeeds or the next scheduled run takes over. Errors a retry can't fix (such as a missing permission) wait for the next scheduled run. Each Items or Customers run first lists every record's name and when it was last changed (one call). If nothing differs from the last run, the run stops there. Deleted records drop out with no further call. Records added, edited, disabled, or renamed are pulled by name in one more call. Full re-sync pulls everything again.

Changes apply from the next scheduled run. Discard changes