Getting custom field after creating with modules api returning 404 sometimes

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 idea why?

Also, What’s the difference between creating custom fields using /rest/atlassian-connect/1/app/module/dynamic instead of POST /rest/api/3/field ?


Hi ValterJnior,

I think we have a similar issue. We are still investigating but as you say, it seems that after sending a POST to that api “/rest/atlassian-connect/1/app/module/dynamic” to create a new dynamic custom field, there is some sort of extra long running task happening in the background before the field is actually there and any calls to the field options api will return exactly that, a 404.

It is like awaiting for the POST “/rest/atlassian-connect/1/app/module/dynamic” to return successful is not enough time for the field to be actually there.


Thanks for sharing your experience @AbrahamCabrera. I really think there are some delays regarding custom fields and Connect dynamic modules as well. I’m facing another issue similar. I’m trying to access my custom fields on the /enabled Webhook and sometimes it works sometimes not. No idea why as well.

In the first case(question case) I had to create some retry operations to make the app work. I hope you’ve found a workaround too.

1 Like