Stephenb,
Apologies for not responding sooner.
Sorry for the confusion. I was just sharing the locations where I discover most of my problems.
In this particular case, since this is related to SNOW to Jira updates, you'd want to check your Flow Designer triggers.
You'd need a flow that triggers from the rm_story table on updates that has a correlation_id or correlation_display, depending on what fields you're using. You'd select the Jira ID from the correlation_id to make the updates. Something like this:
Then you'd reference the triggering file for its correlation id and use that to reference the corresponding Jira issue.
You can add filter conditions as needed to prevent unecessary updates and reduce overhead on the flow and prevent duplicate updates, etc.
Oh, Stephen, one thing I overlooked that you'll definitely want to change. Don't leave the trigger as run once. You'd probably want to change it to "Only if not currently running"
or "For Every Update" and do some testing. That should prevent it from only running one time ever and also from creating duplicates from multiple concurrent changes.
Oh, Stephen, one thing I overlooked that you'll definitely want to change. Don't leave the trigger as run once. You'd probably want to change it to "Only if not currently running"
or "For Every Update" and do some testing. That should prevent it from only running one time ever and also from creating duplicates from multiple concurrent changes.
