Jira - Get Comments: Sometimes fails with code 403

Describe the problem/error/question

We have a Workflow which beside other nodes has a node where we get comments from jira issues. This Node throws sometimes an error and sometimes its working. I contacted Atlassian Support and they said:
Previously Jira and Confluence Cloud APIs simply discarded any body included with an HTTP GET request and continued to process the request as normal, AWS Cloudfront will actively reject such requests

HTTP clients (other than browsers) that attempt to include a body with a GET request will observe an HTTP 403 response code.

Because its a built in node, we cannot check or modify the api request. Maybe someone had a simillar problem and found a solution?

What is the error message (if any)?

ERROR: The request could not be satisfied 403 ERROR The request could not be satisfied. Bad request. We can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront) Request ID: 5w5_x2yls1LmRM3Q3UHIdRwBfItsp6U9rjlFrWiv9pzg-dqrSy0D3Q==

Please share your workflow

{
“nodes”: [
{
“parameters”: {
“resource”: “issueComment”,
“operation”: “getAll”,
“issueKey”: “={{ $json.key }}”,
“returnAll”: true,
“options”: {}
},
“id”: “3e3d651e-de44-489e-a1e2-5de7765d4fd3”,
“name”: “Get Comments”,
“type”: “n8n-nodes-base.jira”,
“typeVersion”: 1,
“position”: [
-560,
1400
],
“alwaysOutputData”: true,
“retryOnFail”: true,
“credentials”: {
“jiraSoftwareCloudApi”: {
“id”: “d4RWWz8Q3byP2km7”,
“name”: “Jira (@.**)”
}
}
}
],
“connections”: {
“Get Comments”: {
“main”: [

]
}
},
“pinData”: {},
“meta”: {
“instanceId”: “1bdc05452ee10f07bb5d95d21830fc9fa62de6562bc60a28fe0c727e4c113537”
}
}

Share the output returned by the last node

We pass $json.key which contains the Issue Key.

Information on your n8n setup

  • n8n version: 1.78.1
  • Database (default: SQLite): n8n Cloud
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud
  • Operating system: n8n Cloud

Please enable Retries in your node.
If that doesn’t work, then you’ll probably need to use an HTTP node.
Please share your workflow inside a code block if you need further assistance.

like this


.

:muscle: If my reply solves your problem, please remember to mark it as a solution.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.