search

PostHog / posthog-plugin-migrator3000

Migrate your events to a new PostHog instance.
MIT License
7 stars 10 forks source link

Default Date From seems to fail #15

Open Mentioum opened 2 years ago

Mentioum commented 2 years ago

What happened

Error from Posthog Cloud Plugin Output

2022-06-30 13:11:00.304 UTC | PLUGIN | ERROR | Error: Unable to determine the lower timestamp bound for the export automatically. Please specify a 'dateFrom' value.     at Proxy.meta.global.initTimestampsAndCursor (/code/plugin-server/dist/worker/vm/upgrades/historical-export/export-historical-events.js:164:23)     at Object.exec (/code/plugin-server/dist/worker/vm/upgrades/historical-export/export-historical-events.js:79:31)     at runMicrotasks (<anonymous>)     at processTicksAndRejections (node:internal/process/task_queues:96:5)     at async runPluginTask (/code/plugin-server/dist/worker/plugins/run.js:88:20)     at async /code/plugin-server/dist/worker/worker.js:49:49     at async /code/plugin-server/node_modules/@posthog/piscina/dist/src/worker.js:149:26
-- | -- | -- | --

Field implies empty is fine

image

Expectation

It exports all events if no date is given (as per field help text)

Mentioum commented 2 years ago

Also when putting an arbitrary date a long time ago you get this error: image

It should probably do a query to find the first event after the time and then do chunks of events from that point forward.

lsmith77 commented 1 year ago

I guess a simpler work-around could also be to just use a date before Posthog even existed? ie. 2020-01-01