I have a Confiforms form that uses an IFTTT (onModify) that creates a Jira ticket, and then a second IFTT saves the result. On Save, the first IFTTT fires when the user has checked a RequestReview checkbox field, and then the second IFTTT fires and stores the return value (the returned Jira ticket object) in a field (JiraLink).
Both of these IFTTTs check the value of this RequestReview checkbox, and the JiraLink field. If the JiraLink field is already populated, then they do not fire. This usually works well.
However, sometimes this fails -- the form correctly creates the Jira ticket, but fails to save the return value in the JiraLink field. So the next time the user edits, it creates a new Jira ticket. This can happen over and over, resulting in what appears (to the user) to be duplicate tickets.
My question, is there some known reason this might happen?
I have been unable to reproduce this when I point the form to a second (Staging) instance of Jira. My theory is that our Production Jira service is not responding quickly enough, and so the first IFTTT has launched the Jira-Create call, but before it completes, the second IFTTT fires and saves a (blank) return value. Is this a possibility? Anything else to look for?
