I'm using an on-prem instance and the built-in JIRA resource. The resource correctly fetches the API schema and will auth with the built-in OAuth flow.
Once you try and run any query against the resource it always just returns error:"fetch failed". Digging into the logs a bit more this is the additional info:
WD: fetch failed
at /retool_backend/bundle/main.js:4253:15989
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async GQh (/retool_backend/bundle/main.js:4513:40843)
at async /retool_backend/bundle/main.js:4513:59026
I've rebuilt the stack, pulled the images again and no luck. Not sure what's causing it at this point. Any suggestions welcome.
In the past I have seen the 'failed to fetch' error pop up in relation to CORS policies for AWS S3 resources.
Users found they could fetch data but were not able to upload or run PUT method calls to their resource, getting the same 'failed to fetch' error in Retool. Which might be why you can grab the Jira API schema but not the query after the OAuth flow.
I would double check the Jira resource to make sure that it has enabled your URL/domain to make requests/Queries.
Is there any more information you can provide about the Retool query that generates this message? Perhaps a screenshot of the query and resource set up?
I found some resource on the Jira forums that could be useful here, here and here.
It seems there are a number of reasons Jira might respond to a request with a failed to fetch on their end you might need to check Jira's logs to see the request being sent in to see if the request has the correct parameters and if it is hitting the server as expected.