neosync
neosync copied to clipboard
Generate UUID for a PK column referenced by other tables with referencing FKs to fail
Bug description
Please describe. Generating UUID for my table resulted in this error in UI / docker worker:
{"time":"2025-03-28T18:03:10.74733593Z","level":"ERROR","msg":"Child processors failed: child processors resulted in zero messages\n","ActivityID":"5","ActivityType":"SyncTable","Attempt":1,"JobRunId":"6365728e-41a8-4ab9-a06c-7795d069eb16-2025-03-28T18:02:47Z","Namespace":"default","RunID":"3f6a0c06-e79b-48e5-a1cc-cb3a418420bc","TaskQueue":"sync-job","WorkerID":"1@db76fceabb15@","WorkflowID":"6365728e-41a8-4ab9-a06c-7795d069eb16-2025-03-28T18:02:47Z-public_customer_invoice_update_1-1743184986683174762","WorkflowType":"TableSync","accountId":"43c71652-b3f7-4dbb-87c2-508075496054","activitySession":"6365728e-41a8-4ab9-a06c-7795d069eb16-2025-03-28T18:02:47Z:acf05757-77f9-4bac-950a-174f4506b11c","benthos":"true","hasContinuationToken":false,"id":"public.customer_invoice.update.1","label":"","metadata":{"Schema":"public","Table":"some_table_name_with_fk"},"path":"root.pipeline.processors.1"}
Turning this column back to passthrough fixes the issue.
Hey would you mind sharing your table setup in this scenario? We have been investigating this for another user but were unable to reproduce it! We've been digging into this for the last few days. if you could provide a minimal table setup to easily repro this it would be invaluable.
Would also be curious to know if you have pulled the latest docker image recently. We have been reworking some of the redis stuff and would be curious to know if that fixes it for you.