Newly created PRB tickets in SNOW are not creating corresponding Jira tickets as per our Exalate Integration Setup. We recently had a Jira Version upgrade tickets created during and after that window is showing as “Waiting for Sync” in the entity sync window and also available in SYNC queue but its not getting updated automatically.

  1. Serhiy Onyshchenko

    Hello, Sarika Bhowte , thanks for raising on community.
    When you have an outgoing sync (in status WAITING_FOR_REMOTE) in queue of one side (let's say for example of SNOW), then there must be a corresponding transaction in the incoming sync queue of the other side (Jira in this example). The outgoing sync is thus blocked until that related remote incoming sync is finished.
    The troubleshooting has to go from there: what's the status of that remote incoming queue?
    Is there an error on remote, blocking it?

    Regards, Serhiy.

  2. Sarika Bhowte

    Thank you for your reply. There are no changes been done which can block the sync both on JIRA as well as on SNOW side.

    Unfortunately, we do not have inhouse Exalate expert who would understand the below error message.

    Error Detail Message: Unparseable date: "[50, 48, 50, 51, 45, 49, 50, 45, 51, 49, 32, 48, 54, 58, 50, 54, 58, 48, 51]"  

    Is there any kind of document or the link where we can see all the possible error message and the solution for the Exalate SNOW-JIRA integration.?



CommentAdd your comment...