Open ckahle33 opened 3 months ago
@ckahle33 It seems related to this issue : https://github.com/tractr/directus-sync/issues/58 I will add tests to reproduce this bug and fix it.
I also just experienced this bug - deleting the flow in question is a temporary fix :)
Same issue here
Describe the bug We are using quite a few flows, and depending on the UUIDs in different environments etc, we frequently see the error:
running
update directus_operations set resolve = NULL, reject = NULL;
will fix this error and will then write the correct operation fk value in those columns on the nextnpx directus-sync push
.It is possible that this is a directus bug from earlier versions where the db state can be "corrupt" in a way where old deleted operations are still being referenced from
directus_operations.resolve
anddirectus_operations.reject
columns.Thank you for taking a look at this. We rely on this tool to sync flow and schema state across environments, and it has been excellent and very useful so far.
To Reproduce Steps to reproduce the behavior:
directus-sync push -c ./directus-sync.local.config.cjs
Expected behavior In some cases
directus-sync push
will retry to reconcile foreign key relations, which in this case, is not happeningVersions (please complete the following information):
^1.5.3
10.11.0