nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way to increase the number of Jira issues that a confiform can create?

Brian Karst

I seem to have come to a threshold of 64 (When I need 86). After submission and some time passes I get the error: "Operation has failed. Error communicating with the server. Gateway Time-out (error). Please check Confluence server logs for more details." Looking into the project, I see that 64 of my 86 issues were created even though the error doesn't tell you that.

Accepted answers

Alex Medved _ConfiForms_

Are you attempting to create 86 issues in Jira on ConfiForms form submit!?

ConfiForms has a limit of 200 IFTTTs per request / submission (which is really a lot and should never be exceeded or be even close).

If you exceed that then it will fail to process any other IFTTTs.

What happens in your case is like the timeout between front end server and Confluence (as it is running a very long and time consuming task)

Alex

All comments

Alex Medved _ConfiForms_

Are you attempting to create 86 issues in Jira on ConfiForms form submit!?

ConfiForms has a limit of 200 IFTTTs per request / submission (which is really a lot and should never be exceeded or be even close).

If you exceed that then it will fail to process any other IFTTTs.

What happens in your case is like the timeout between front end server and Confluence (as it is running a very long and time consuming task)

Alex

Brian Karst

Yes Alex I am. Technically I am creating 1 issue, pulling the key out and creating 85 sub tasks for that issue. The 200 IFTTTs limit is not a limit in the form/page is it? A little more detail into what I have been tasked to do, and knowing that my knowledge in Confluence, Jira, and ConfiForms could be termed barbaric. ie. there is 0 elegance to how I am accomplishing it I am sure.

We are exploring ways to utilize Confluence/Jira and are utilizing the "ticketing" nature of Jira and are going to utilize it to track the development of our people and others within our organization. I am looking at 7 different development programs with up to 85 items to be completed. Which will far exceed 200 IFTTTs in the form, but never that many submitted at once.

So far I have the ConfiForm submitting all the information without errors (finally, that was brutal) It creates the Parent Issue depending upon the entry category and creates 63 of the 85 sub tasks and I receive the error. Which I believe to be correct, it is a timeout error, even though only 15-20 seconds elapse; if it just gave it 30 seconds. Is there anything you would recommend other than finding someone who can look into gateway timing for me?

Alex Medved _ConfiForms_

ConfiForms has a 180 seconds timeout for the form submission

This cannot be changed (and in our opinion that should not be ever exceeded). The form shall submit in 2-5 seconds for good usability. If you form takes longer to submit it starts to feel like something is broken

I dont really know why there is a need to do what you do and cannot comment on that, but what you describe sounds like a timeout between app server and confluence.

Brian Karst

Alex, in case you would like to know, it was throwing a bad error. There was an extra quotation mark on a field in the JSON of the IFTTT it was failing at. Also, it takes approximately 2 minutes for the 86 issues to be created

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server

jira

confiforms