Stop sync if issue is removed from DB (doesn't exist)

Originally asked by Andrew on 27 May 2022 (original question)


Hello community,

I have issue that at some point in process in SN, issue is removed from SN DB. Issue was previously linked to other issue in Jira. Now when update comes from Jira, error on SN side appears, ex: “Exalate couldn’t find local issue GAPRV0042354 (48f6b10c1b7b0994385832219b4bcb95) to run the Exalate Scripts.”

How to stop sync if issue doesn’t exist ?


Answer by Jose Pablo Alpizar Hidalgo on 08 September 2022

Please notice that with our Clean-up tools you should be able to stop any synchronization immediately without processing sync requests that are in the Sync Queue.
Just reference the following article and review the clean up by issue option to apply in your case.