5 comments

[ 5.0 ms ] story [ 17.7 ms ] thread
(comment deleted)
I tried to integrate conductor in a project I’m working on but when starting a workflow the idempotency key was ignored, so sending the same key twice started two workflows with different id’s. I found that pretty strange but apparently that param disappears somewhere in the plumbing of the conductor project itself. Somewhat surprised the article doesn’t mention it.

I switched over to Temporal, and so far pretty happy about it.

We actually didn't get as far as testing idempotency tokens, I'm afraid! Material for a future writeup, perhaps. :-)
OSS Conductor does not support idempotency keys. Orkes Conductor which is an enterprise SaaS does however, support idempotency keys.