Continue on error with Jira node

Questions
1

Describe the problem/error/question

I built a workflow that creates Jira tickets based on Google Forms. The users submit the Google Form, which creates entries in a linked GSheet. Then the n8n workflow looks at this GSheet and creates tickets based on the responses.

The workflow is running on a schedule, and filters only for rows that do not have a Jira issue key yet. This is the part that is causing the problem. If multiple tickets have to be created, and one of them has an error in Jira, the whole process stops, and the sheet doesn’t get updated. The tickets before the error still get created, but the sheet doesn’t update, so n8n will pick them up next time as well, resulting in an infinite loop.

What I want to achieve is to somehow recognize that there is an issue with a ticket, and if that happens, update the sheet with some custom error message (can also be the output of the Jira node on error). Something like: if Jira error, then set issueKey property to error message

I tried both “continue on error” and “always output data” settings, but neither work as I expect them to.

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 0.229.0
  • Database (default: SQLite): PostgreSQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own, main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker & kubernetes
  • Operating system: linux
3

Hi @mako, you could consider splitting your list of Jira tickets into batches of 1 using the Split in Batches node. This means the Jira node would only process a single item at a given time and you can implement your If logic afterwards. I’ve suggested something similar over here for Baserow, and it sounds like the basic workflow design should work in your case as well.

3 Likes
4

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