Hi @Pedro Machado - thanks for brining this up; this is a known bug (there's a PR open to fix it); we expect it to go out with the next release. In the meantime you can provide an explicit
idempotency_key
to prevent subsequent registrations when you know changes haven't been made.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.