backup failed: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined

[z83546263]

Plugin Version

1.1.0-beta.10

OpenClaw Version

2026.4.12-beta.1

Bug Description

2026-04-21T16:53:14.688+08:00 [plugins] memory-lancedb-pro: backup failed: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined

Expected Behavior

2026-04-21T16:53:14.688+08:00 [plugins] memory-lancedb-pro: backup failed: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined

Steps to Reproduce

2026-04-21T16:53:14.688+08:00 [plugins] memory-lancedb-pro: backup failed: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined

Error Logs / Screenshots

Embedding Provider

None

OS / Platform

No response

[AliceLJY]

Thanks for the report. I checked the backup path in current code: the failure is most likely coming from the auto-backup block building:

api.resolvePath(join(resolvedDbPath, "..", "backups"))

If resolvedDbPath or api.resolvePath(...) is undefined in this runtime, node:path.join() will throw exactly this ERR_INVALID_ARG_TYPE.

Two quick data points would help pin whether this is config parsing or an OpenClaw resolvePath/runtime change:

1. the startup log line that looks like memory-lancedb-pro@... plugin registered (db: ...)
2. your plugins.entries.memory-lancedb-pro.config.dbPath value, if you set one

This backup failure should not block normal memory reads/writes, but it means daily JSONL backup is not being created. Marking this as a real backup-path bug; the likely fix is to guard resolvedDbPath/resolvePath and fall back to getDefaultDbPath() before scheduling backup.