# Record not getting created in JIRA

**URL:** <https://community.exalate.com/t/record-not-getting-created-in-jira/4102>\
**Category:** General Questions\
**Tags:** migrated\_question, onpremise-hpalm, create-issue\
**Created:** [November 4, 2024, 6:30am UTC](https://community.exalate.com/t/record-not-getting-created-in-jira/4102 "2024-11-04T06:30:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 4, 2024, 6:30am UTC](https://community.exalate.com/t/record-not-getting-created-in-jira/4102/1 "2024-11-04T06:30:45Z")

</div>

_Originally asked by SANDEEP ADE on 10 October 2019 [(original question)](https://oldcommunity.exalate.com/questions/3704251)_

* * *

Hi,

We have defects waiting in outgoing queue since long time in ALM ,in Jira these records are not shown in the incoming sync queue.

There are no errors shown in either ALM side of exalate or JIRA Exalate .

In ALM Exalate ,the records are present in the outgoing queue but in JIRA ,the records are not present

* * *

#### Comments:

> **SANDEEP ADE commented on 10 October 2019**
>
> > also attaching screenshots from jira ![](https://dub1.discourse-cdn.com/flex018/download/attachments/3704255/GWEDEF%20Project%202.PNG?version=1&modificationDate=1570719741113&api=v2) ![](https://dub1.discourse-cdn.com/flex018/download/attachments/3704255/GWEDEF%20Project.PNG?version=1&modificationDate=1570719741403&api=v2) ![](https://dub1.discourse-cdn.com/flex018/download/attachments/3704255/Syn%20Queue.PNG?version=1&modificationDate=1570719741715&api=v2)

---

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 4, 2024, 6:30am UTC](https://community.exalate.com/t/record-not-getting-created-in-jira/4102/2 "2024-11-04T06:30:47Z")

</div>

_Answer by Francis Martens (Exalate) on 10 October 2019_

It looks like that for some reason the sync for these defects is broke.

Can you cleanup the syncs

* * *

#### Comments:

> **SANDEEP ADE commented on 10 October 2019**
>
> > i did and tried to re-sync (by updating comment)
> 
> it again behaving the same way

> **SANDEEP ADE commented on 10 October 2019**
>
> > is there is a chance the process is running slow and restart will fix issue?

> **Francis Martens (Exalate) commented on 10 October 2019**
>
> > hmm
> 
> Can you raise an issue on our support channel,
> 
> There is no such thing as a sync running slow.
> 
> I will be reaching out to dive into the details and understand what’s going on

> **SANDEEP ADE commented on 10 October 2019**
>
> > i already raised the ticket and sent the support files from alm and Jira EASE-3209

> **Francis Martens (Exalate) commented on 11 October 2019**
>
> > OK - let’s take it from there