# Atlassian Connect Express: the /enabled webhook is called before jiraIssueFields are created

**URL:** <https://community.developer.atlassian.com/t/atlassian-connect-express-the-enabled-webhook-is-called-before-jiraissuefields-are-created/58102>\
**Category:** Jira Cloud\
**Tags:** connect-descriptor, ac-express, lifecycle, custom-field\
**Created:** [May 6, 2022, 3:40pm UTC](https://community.developer.atlassian.com/t/atlassian-connect-express-the-enabled-webhook-is-called-before-jiraissuefields-are-created/58102 "2022-05-06T15:40:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![FaridKhaheshi](https://avatars.discourse-cdn.com/v4/letter/f/cdc98d/32.png) [@FaridKhaheshi](https://community.developer.atlassian.com/u/FaridKhaheshi)\
**Post date:** [May 6, 2022, 3:40pm UTC](https://community.developer.atlassian.com/t/atlassian-connect-express-the-enabled-webhook-is-called-before-jiraissuefields-are-created/58102/1 "2022-05-06T15:40:01Z")

</div>

We have a Jira App on Atlassian Marketplace.  
We do some cleanup/sync jobs after each installation. This preparation includes updating some `jiraIssueFields` defined in the descriptor.  
Recently, we have noticed that for about 50% of new installations, the `/enabled` webhook is called before those issue fields are created. So we get the following error when we call the `/rest/api/2/field` REST endpoint:

```auto

The field with the given key does not exist or does not support options

```

Is there any way other than polling JIRA’s REST API to receive an update when all fields defined in the descriptor are created?

---

<div class="post-metadata">

**Author:** ![leonardonunes](https://avatars.discourse-cdn.com/v4/letter/l/e47774/32.png) [@leonardonunes](https://community.developer.atlassian.com/u/leonardonunes)\
**Post date:** [May 6, 2022, 4:55pm UTC](https://community.developer.atlassian.com/t/atlassian-connect-express-the-enabled-webhook-is-called-before-jiraissuefields-are-created/58102/2 "2022-05-06T16:55:30Z")

</div>

Hi @FaridKhaheshi we are also facing this same problem. We opened a ticket with Atlassian, they have already replied and said that they were able to reproduce the problem. We are still waiting for more information on when they’re fixing it.

The problem happens like you said, on **/enabled** webhook, but it also happens if you create the field using this API: **/rest/atlassian-connect/1/app/module/dynamic**. If you try to search for the created field sometimes it says that it does not exist.

Here a post I also made here on the community:

> [@Getting custom field after creating with modules api returning 404 sometimes](https://community.developer.atlassian.com/t/getting-custom-field-after-creating-with-modules-api-returning-404-sometimes/57280):
>
> Hello everyone, I’m facing an issue using jira rest api with a connect app and would like to know if someone already saw this behavior or some similar. I’m facing the issue of creating custom fields through this api: /rest/atlassian-connect/1/app/module/dynamic and trying to add new options or remove old options using /rest/api/3/field options API, but returns 404 sometimes like it wasn’t created yet or it was taking some time to other api’s recognize the creation of a new custom field. Any ide…

---

<div class="post-metadata">

**Author:** ![GabrielDias](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@GabrielDias](https://community.developer.atlassian.com/u/GabrielDias)\
**Post date:** [May 12, 2022, 5:04pm UTC](https://community.developer.atlassian.com/t/atlassian-connect-express-the-enabled-webhook-is-called-before-jiraissuefields-are-created/58102/3 "2022-05-12T17:04:12Z")

</div>

Hi @FaridKhaheshi , it looks like there was a deployment that caused this issue. We’ve been analyzing it with our engineering teams and we’ll let you know once we have any news.

Best,  
Gabriel