[Wordpress] Unexpected end of JSON input

Describe the issue/error/question

I use N8N and the DeepL node to ingest a RSS feed with near live Telegram Posts
it’s my 5 month old project to translate & make accessible the War in Ukraine.

RSS Source if you want to test with live data :

  1. RU Militants via Observer on Inoreader
  2. UA AmplifyUkraine via SlavaUkraini on Inoreader

Is it because of the original Russian or Ukrainian characters, or maybe the emoji’s ?
I’m not sure because overall all of my posts do get posted on wordpress, even tho instead of running for a few minutes, the time it takes for the exact same data to go Discord, Telegram or else, on Wordpress it can take up to 20 minutes to run the workflow and if I retry, it only gets worse, it seems also to me that the latest upgrade may have made this severe because i’m definitely seeing a difference with the last two minor versions, while 3 months ago it felt like Wordpress publishing was as fast as the others? it’s probably my own bias deteriorating my perception since I’ve tried different things to solve this but to no avail, it seems random but I don’t see any difference with JSON objects that do get published.

Or perhaps it’s the worpress having +200K posts since 5 month ?

to resume: the exact same data structure and JSON objects get posted to Telegram or Discord just fine

What is the error message (if any)?

Jul 24 19:03:28 2022-07-24T17:03:28.701Z | verbose | Workflow execution finished with error "{\n error: {\n message: 'Unexpected end of JSON input',\n stack: 'SyntaxError: Unexpected end of JSON input\\n' +\n ' at JSON.parse (<anonymous>)\\n' +\n ' at Object.execute (/app/code/node_modules/n8n-nodes-base/dist/nodes/StopAndError/StopAndError.node.js:91:38)\\n' +\n ' at Workflow.runNode (/app/code/node_modules/n8n-workflow/dist/src/Workflow.js:594:51)\\n' +\n ' at /app/code/node_modules/n8n-core/dist/src/WorkflowExecute.js:557:68\\n' +\n ' at processTicksAndRejections (node:internal/process/task_queues:96:5)'\n },\n workflowId: '74',\n file: 'WorkflowExecute.js',\n function: 'processSuccessExecution'\n}"

Please share the workflow

The workflow is super simple, I just use a merge to have the original data in full along with the translation so I can “compose” my wordpress post fields with all the different JSON items, it works great most of the time : https://ruprop.live | https://amplifyrukaine.eu and with plenty of flags or smileys and cyrilc characters, I’m lost on what provoques this error.

Share the output returned by the last node

[
  {
    "id": 460620,
    "date": "2022-07-24T19:02:34",
    "date_gmt": "2022-07-24T17:02:34",
    "guid": {
      "rendered": "https://ruprop.live/the-ministry-of-foreign-affairs-of-canada-stated-that-it-was-aware-of-the-death-of-a-canadian-in-ukraine-earlier-the-politico-newspaper-reported-that-a-group-of-mercenaries-consisting-of-two-me-3/",
      "raw": "https://ruprop.live/the-ministry-of-foreign-affairs-of-canada-stated-that-it-was-aware-of-the-death-of-a-canadian-in-ukraine-earlier-the-politico-newspaper-reported-that-a-group-of-mercenaries-consisting-of-two-me-3/"
    },
    "modified": "2022-07-24T19:02:34",
    "modified_gmt": "2022-07-24T17:02:34",
    "password": "",
    "slug": "the-ministry-of-foreign-affairs-of-canada-stated-that-it-was-aware-of-the-death-of-a-canadian-in-ukraine-earlier-the-politico-newspaper-reported-that-a-group-of-mercenaries-consisting-of-two-me-3",
    "status": "publish",
    "type": "post",
    "link": "https://ruprop.live/the-ministry-of-foreign-affairs-of-canada-stated-that-it-was-aware-of-the-death-of-a-canadian-in-ukraine-earlier-the-politico-newspaper-reported-that-a-group-of-mercenaries-consisting-of-two-me-3/",
    "title": {
      "raw": "The Ministry of Foreign Affairs of Canada stated that it was aware of the death of a Canadian in Ukraine.  \n  \nEarlier, the Politico newspaper reported that a group of mercenaries consisting of two me - Повёрнутые на Z войне 🇷🇺",
      "rendered": "The Ministry of Foreign Affairs of Canada stated that it was aware of the death of a Canadian in Ukraine.  \n  \nEarlier, the Politico newspaper reported that a group of mercenaries consisting of two me &#8211; Повёрнутые на Z войне 🇷🇺"
    },
    "content": {
      "raw": "TRANSLATION :\nThe Ministry of Foreign Affairs of Canada stated that it was aware of the death of a Canadian in Ukraine.  \n  \nEarlier, the Politico newspaper reported that a group of mercenaries consisting of two men from the US, a Canadian and a Swedish citizen who had been fighting in Ukraine on Kiev's side were killed this week.\nSource : Повёрнутые на Z войне 🇷🇺\nLink : https://t.me/voenacher/25670\nDate : 2022-07-24T16:50:08.000Z\nORIGINAL :\n<br /><strong>Министерство иностранных дел Канады заявило, что ему известно о гибели канадца на Украине</strong>.<br /> \n<br /> \nРанее газета Politico сообщила, что группа наемников в составе двух человек из США, канадца и гражданина Швеции, воевавших на Украине на стороне Киева, были уничтожены на текущей неделе.",
      "rendered": "<p>TRANSLATION :<br />\nThe Ministry of Foreign Affairs of Canada stated that it was aware of the death of a Canadian in Ukraine.  </p>\n<p>Earlier, the Politico newspaper reported that a group of mercenaries consisting of two men from the US, a Canadian and a Swedish citizen who had been fighting in Ukraine on Kiev&#8217;s side were killed this week.<br />\nSource : Повёрнутые на Z войне 🇷🇺<br />\nLink : <a href=\"https://t.me/voenacher/25670\" rel=\"nofollow\">https://t.me/voenacher/25670</a><br />\nDate : 2022-07-24T16:50:08.000Z<br />\nORIGINAL :<br />\n<br /><strong>Министерство иностранных дел Канады заявило, что ему известно о гибели канадца на Украине</strong>.</p>\n<p>Ранее газета Politico сообщила, что группа наемников в составе двух человек из США, канадца и гражданина Швеции, воевавших на Украине на стороне Киева, были уничтожены на текущей неделе.</p>\n",
      "protected": false,
      "block_version": 0
    },
    "excerpt": {
      "raw": "",
      "rendered": "<p>TRANSLATION : The Ministry of Foreign Affairs of Canada stated that it was aware of the death of a Canadian in Ukraine. Earlier, the Politico newspaper reported that a group of mercenaries consisting of two men from the US, a Canadian and a Swedish citizen who had been fighting in Ukraine on Kiev&#8217;s side were [&hellip;]</p>\n",
      "protected": false
    },
    "author": 1,
    "featured_media": 0,
    "comment_status": "open",
    "ping_status": "open",
    "sticky": false,
    "template": "",
    "format": "standard",
    "meta": [],
    "categories": [
      48
    ],
    "tags": [],
    "permalink_template": "https://ruprop.live/%postname%/",
    "generated_slug": "the-ministry-of-foreign-affairs-of-canada-stated-that-it-was-aware-of-the-death-of-a-canadian-in-ukraine-earlier-the-politico-newspaper-reported-that-a-group-of-mercenaries-consisting-of-two-me-3",
    "_links": {
      "self": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "collection": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts"
        }
      ],
      "about": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/types/post"
        }
      ],
      "author": [
        {
          "embeddable": true,
          "href": "https://ruprop.live/wp-json/wp/v2/users/1"
        }
      ],
      "replies": [
        {
          "embeddable": true,
          "href": "https://ruprop.live/wp-json/wp/v2/comments?post=460620"
        }
      ],
      "version-history": [
        {
          "count": 0,
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620/revisions"
        }
      ],
      "wp:attachment": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/media?parent=460620"
        }
      ],
      "wp:term": [
        {
          "taxonomy": "category",
          "embeddable": true,
          "href": "https://ruprop.live/wp-json/wp/v2/categories?post=460620"
        },
        {
          "taxonomy": "post_tag",
          "embeddable": true,
          "href": "https://ruprop.live/wp-json/wp/v2/tags?post=460620"
        }
      ],
      "wp:action-publish": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-sticky": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-assign-author": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-create-categories": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-assign-categories": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-create-tags": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-assign-tags": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "curies": [
        {
          "name": "wp",
          "href": "https://api.w.org/{rel}",
          "templated": true
        }
      ]
    }
  }
]

Information on your n8n setup

  • n8n version: n8n 0.187.2
  • Database you’re using (default: SQLite): Postgres
  • Running n8n with the execution process [own(default), main]: own
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
  • Wordpress is running on the same VPS also using Docker, nothing particular in terms of plugins

Hi @jon It’s probably holiday time but I was wondering if we could have a look into this ?

…am I invisible ?

Hi @benb, perhaps you can narrow down your example workflow a bit to just the Wordpress node (and a Set node defining a single item for which the error occurs) so this can be easily reproduced?

If you enable debug logging for your instance, is there any additional information in your server logs about your error?

Hi @MutedJam thanks for your support.

I have no idea how to proceed your request to be honest. This is a live production workflow, how can I narrow it down ?

This is the error provided with debug level log enabled :

Ah sorry for that, I missed the log level part in your output.

It might be worth checking if you can reproduce it outside of your production environment. I don’t have a Wordpress test instance or Deepl account ready I am afraid, so it would be a great help if you can find an item that is causing the problem you have described.

1 Like

All I know is that, all my wordpress worflows suffer the exact same issue, which is impossible to debug because, beside that error above, which does not give much, there are no errors in the UI, the worflows takes ages to “finish” if at all, very often I have to stop them manually, but there is no error per se, they just keep going on and on, even tho the posts themselves, at least part of them, it’s impossible to know how much, are indeed published at the target.

So you could consider moving the Wordpress node into it’s own sub-workflow (and call that sub-workflow via the Execute Workflow node for each batch of 1).

By doing so you’d get separate execution logs for each sub-workflow execution (= for each item sent to Wordpress) and should be able to more easily identify the payload causing the problem.

I will try following what you suggest, meanwhile I’m proposing to share my credentials in private, otherwise i’m not sure we’ll ever find the culprit here.

Well, this provided in the OP, is a a payload causing the problem :
i’v extracted it from one of the workflow after an error, but like I said in the OP, there is no fundamental different between this JSON block and 90% of the JSON payloads that do get published in both my wordpress.

[
  {
    "id": 460620,
    "date": "2022-07-24T19:02:34",
    "date_gmt": "2022-07-24T17:02:34",
    "guid": {
      "rendered": "https://ruprop.live/the-ministry-of-foreign-affairs-of-canada-stated-that-it-was-aware-of-the-death-of-a-canadian-in-ukraine-earlier-the-politico-newspaper-reported-that-a-group-of-mercenaries-consisting-of-two-me-3/",
      "raw": "https://ruprop.live/the-ministry-of-foreign-affairs-of-canada-stated-that-it-was-aware-of-the-death-of-a-canadian-in-ukraine-earlier-the-politico-newspaper-reported-that-a-group-of-mercenaries-consisting-of-two-me-3/"
    },
    "modified": "2022-07-24T19:02:34",
    "modified_gmt": "2022-07-24T17:02:34",
    "password": "",
    "slug": "the-ministry-of-foreign-affairs-of-canada-stated-that-it-was-aware-of-the-death-of-a-canadian-in-ukraine-earlier-the-politico-newspaper-reported-that-a-group-of-mercenaries-consisting-of-two-me-3",
    "status": "publish",
    "type": "post",
    "link": "https://ruprop.live/the-ministry-of-foreign-affairs-of-canada-stated-that-it-was-aware-of-the-death-of-a-canadian-in-ukraine-earlier-the-politico-newspaper-reported-that-a-group-of-mercenaries-consisting-of-two-me-3/",
    "title": {
      "raw": "The Ministry of Foreign Affairs of Canada stated that it was aware of the death of a Canadian in Ukraine.  \n  \nEarlier, the Politico newspaper reported that a group of mercenaries consisting of two me - Повёрнутые на Z войне 🇷🇺",
      "rendered": "The Ministry of Foreign Affairs of Canada stated that it was aware of the death of a Canadian in Ukraine.  \n  \nEarlier, the Politico newspaper reported that a group of mercenaries consisting of two me &#8211; Повёрнутые на Z войне 🇷🇺"
    },
    "content": {
      "raw": "TRANSLATION :\nThe Ministry of Foreign Affairs of Canada stated that it was aware of the death of a Canadian in Ukraine.  \n  \nEarlier, the Politico newspaper reported that a group of mercenaries consisting of two men from the US, a Canadian and a Swedish citizen who had been fighting in Ukraine on Kiev's side were killed this week.\nSource : Повёрнутые на Z войне 🇷🇺\nLink : https://t.me/voenacher/25670\nDate : 2022-07-24T16:50:08.000Z\nORIGINAL :\n<br /><strong>Министерство иностранных дел Канады заявило, что ему известно о гибели канадца на Украине</strong>.<br /> \n<br /> \nРанее газета Politico сообщила, что группа наемников в составе двух человек из США, канадца и гражданина Швеции, воевавших на Украине на стороне Киева, были уничтожены на текущей неделе.",
      "rendered": "<p>TRANSLATION :<br />\nThe Ministry of Foreign Affairs of Canada stated that it was aware of the death of a Canadian in Ukraine.  </p>\n<p>Earlier, the Politico newspaper reported that a group of mercenaries consisting of two men from the US, a Canadian and a Swedish citizen who had been fighting in Ukraine on Kiev&#8217;s side were killed this week.<br />\nSource : Повёрнутые на Z войне 🇷🇺<br />\nLink : <a href=\"https://t.me/voenacher/25670\" rel=\"nofollow\">https://t.me/voenacher/25670</a><br />\nDate : 2022-07-24T16:50:08.000Z<br />\nORIGINAL :<br />\n<br /><strong>Министерство иностранных дел Канады заявило, что ему известно о гибели канадца на Украине</strong>.</p>\n<p>Ранее газета Politico сообщила, что группа наемников в составе двух человек из США, канадца и гражданина Швеции, воевавших на Украине на стороне Киева, были уничтожены на текущей неделе.</p>\n",
      "protected": false,
      "block_version": 0
    },
    "excerpt": {
      "raw": "",
      "rendered": "<p>TRANSLATION : The Ministry of Foreign Affairs of Canada stated that it was aware of the death of a Canadian in Ukraine. Earlier, the Politico newspaper reported that a group of mercenaries consisting of two men from the US, a Canadian and a Swedish citizen who had been fighting in Ukraine on Kiev&#8217;s side were [&hellip;]</p>\n",
      "protected": false
    },
    "author": 1,
    "featured_media": 0,
    "comment_status": "open",
    "ping_status": "open",
    "sticky": false,
    "template": "",
    "format": "standard",
    "meta": [],
    "categories": [
      48
    ],
    "tags": [],
    "permalink_template": "https://ruprop.live/%postname%/",
    "generated_slug": "the-ministry-of-foreign-affairs-of-canada-stated-that-it-was-aware-of-the-death-of-a-canadian-in-ukraine-earlier-the-politico-newspaper-reported-that-a-group-of-mercenaries-consisting-of-two-me-3",
    "_links": {
      "self": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "collection": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts"
        }
      ],
      "about": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/types/post"
        }
      ],
      "author": [
        {
          "embeddable": true,
          "href": "https://ruprop.live/wp-json/wp/v2/users/1"
        }
      ],
      "replies": [
        {
          "embeddable": true,
          "href": "https://ruprop.live/wp-json/wp/v2/comments?post=460620"
        }
      ],
      "version-history": [
        {
          "count": 0,
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620/revisions"
        }
      ],
      "wp:attachment": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/media?parent=460620"
        }
      ],
      "wp:term": [
        {
          "taxonomy": "category",
          "embeddable": true,
          "href": "https://ruprop.live/wp-json/wp/v2/categories?post=460620"
        },
        {
          "taxonomy": "post_tag",
          "embeddable": true,
          "href": "https://ruprop.live/wp-json/wp/v2/tags?post=460620"
        }
      ],
      "wp:action-publish": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-sticky": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-assign-author": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-create-categories": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-assign-categories": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-create-tags": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "wp:action-assign-tags": [
        {
          "href": "https://ruprop.live/wp-json/wp/v2/posts/460620"
        }
      ],
      "curies": [
        {
          "name": "wp",
          "href": "https://api.w.org/{rel}",
          "templated": true
        }
      ]
    }
  }
]

So I tried running this against my own page using your example payload and the Wordpress node from your workflow (the only changes made where the category which doesn’t exist on my instance and the status):

I didn’t run into any problem though I am afraid so wasn’t able to reproduce the problem you have reported.

If you suspect it’s the large number of requests sent to your Wordpress instance in a relatively short amount of time you could consider adding a Wait node in your loop to reduce the load.

Well, that’s exactly why I’m here…after a chat with your CEO on twitter about this :confused:

get this : from the exact same data at the source of the workflow, there is absolutely no issue finishing this workflow in a few seconds up to a few minutes and sending the result to Telegram, Discord or anywhere else.

This problem, is only happening with Wordpress node.

Well…There is already a batch+wait node allowing the wordpress node to create posts accordingly.

i have tried different things : set batch to 1 and have the wait node to wait a few seconds/minutes before next post creation. (same problem)

So I have tested, a batch of 10 posts and & wait for seconds/minutes to check the difference (same problem)

Then I tested a batch of 20, the point is, it does not make any difference, posts do get created, sometimes I can find a the payload provoking the error, most of the time I don’t because, there is no error, the main error, and maybe I should change the title of this forum thread is that every Wordpress workflow, takes eons to complete, if they complete at all.

By the way, the workflow has been disassembled since that twitter exchange the other day, right now this workflow only does translation and publication to wordpress; nothing else, telegram or discord publishing is done on separate worflow, with the exact same data, just fine.

the only thing I could still do, is to test this with a brand new wordpress, but I already know it’s probably gonna work, the question is how to I debug this further to find the real issue here, certainly 40 mins workflow that never end and do not give any hint about why it’s taking that long to process is a problem, maybe the Wordpress node is not ready for such amount of data ?

maybe the fact the wordpress contains thousands of posts in the database is at the source of the problem?

Honestly I have already tried many things to try to figure this out but none of them make a difference.

Even if I connect the wordpress directly at the exit of the translation/merge node, i’m still getting the same problem…

I am very sorry to hear this but without being able to reproduce the problem I am stuck here myself.

If your workflow this is working fine with a fresh Wordpress instance you at least know the problem is with the existing instance behaving differently.

If you’d like to take take the Wordpress node completely out of the equation, you can consider using the HTTP Request node to send the API call to create the post.

It might also be worth monitoring your server’s memory and CPU consumption, checking if one of these might be the bottleneck here when processing a large number of items.

I’ve set the wordpress node into it’s own workflow and use the “execute workflow” node at the end of the previous one to trigger wordpress publishing :

a JSON payload making an error :

Jul 26 13:25:17 2022-07-26T11:25:17.954Z | debug | Request proxied to Axios failed "{\n error: Error: Request failed with status code 400\n at createError (/app/code/node_modules/axios/lib/core/createError.js:16:15)\n at settle (/app/code/node_modules/axios/lib/core/settle.js:17:12)\n at IncomingMessage.handleStreamEnd (/app/code/node_modules/axios/lib/adapters/http.js:269:11)\n at IncomingMessage.emit (node:events:539:35)\n at endReadableNT (node:internal/streams/readable:1345:12)\n at processTicksAndRejections (node:internal/process/task_queues:83:21) {\n config: {\n url: 'https://www.inoreader.com/tgcdn/media/insiderUKR/37470/preview/thumb.jpeg',\n method: 'get',\n headers: [Object],\n transformRequest: [Array],\n transformResponse: [Function (anonymous)],\n paramsSerializer: [Function (anonymous)],\n timeout: 3600000,\n adapter: [Function: httpAdapter],\n responseType: 'arraybuffer',\n xsrfCookieName: 'XSRF-TOKEN',\n xsrfHeaderName: 'X-XSRF-TOKEN',\n maxContentLength: Infinity,\n maxBodyLength: Infinity,\n httpsAgent: [Agent],\n validateStatus: [Function: validateStatus],\n transitional: [Object],\n data: undefined\n },\n request: ClientRequest {\n _events: [Object: null prototype],\n _eventsCount: 7,\n _maxListeners: undefined,\n outputData: [],\n outputSize: 0,\n writable: true,\n destroyed: false,\n _last: true,\n chunkedEncoding: false,\n shouldKeepAlive: false,\n maxRequestsOnConnectionReached: false,\n _defaultKeepAlive: true,\n useChunkedEncodingByDefault: false,\n sendDate: false,\n _removedConnection: false,\n _removedContLen: false,\n _removedTE: false,\n _contentLength: 0,\n _hasBody: true,\n _trailer: '',\n finished: true,\n _headerSent: true,\n _closed: false,\n socket: [TLSSocket],\n _header: 'GET /tgcdn/media/insiderUKR/37470/preview/thumb.jpeg HTTP/1.1\\r\\n' +\n 'Accept: application/json,text/html,application/xhtml+xml,application/xml,text/*;q=0.9, image/*;q=0.8, */*;q=0.7\\r\\n' +\n 'User-Agent: axios/0.21.4\\r\\n' +\n 'Host: www.inoreader.com\\r\\n' +\n 'Connection: close\\r\\n' +\n '\\r\\n',\n _keepAliveTimeout: 0,\n _onPendingData: [Function: nop],\n agent: [Agent],\n socketPath: undefined,\n method: 'GET',\n maxHeaderSize: undefined,\n insecureHTTPParser: undefined,\n path: '/tgcdn/media/insiderUKR/37470/preview/thumb.jpeg',\n _ended: true,\n res: [IncomingMessage],\n aborted: false,\n timeoutCb: null,\n upgradeOrConnect: false,\n parser: null,\n maxHeadersCount: null,\n reusedSocket: false,\n host: 'www.inoreader.com',\n protocol: 'https:',\n _redirectable: [Writable],\n [Symbol(kCapture)]: false,\n [Symbol(kNeedDrain)]: false,\n [Symbol(corked)]: 0,\n [Symbol(kOutHeaders)]: [Object: null prototype]\n },\n response: {\n status: 400,\n statusText: 'Bad Request',\n headers: [Object],\n config: [Object],\n request: [ClientRequest],\n data: <Buffer 7b 22 6d 65 73 73 61 67 65 22 3a 22 52 65 71 75 65 73 74 20 66 61 69 6c 65 64 20 77 69 74 68 20 73 74 61 74 75 73 20 63 6f 64 65 20 34 30 30 22 2c 22 ... 1126 more bytes>\n },\n isAxiosError: true,\n toJSON: [Function: toJSON]\n },\n file: 'NodeExecuteFunctions.js'\n}"

By making the Wordress publication into a sub-process, it created 20 posts in 7 minutes where previously it would last for 30 or 40 minutes, without finishing.

i don’t get it.

CPU

10 vCPU Cores

RAM

60 GB RAM

Memory Consumption : (has 3GB available if needed)

CPU / VPS used


Weirdly enough, this error suggests a problem opening the URL https://www.inoreader.com/tgcdn/media/insiderUKR/37470/preview/thumb.jpeg, so outside of Wordpress itself.

I don’t know where this URL comes from though, it doesn’t seem to be part of the RSS feed https://www.inoreader.com/stream/user/1005324229/tag/Telegram from your original workflow.

These images do come from the RSS feed of course, they are part of each “description” for each feed :

RSS feed : Militants via Observer on Inoreader
Same for the RSS feed on the OP

But I’m not sure why the URL even need to be open, since all the N8N is doing is to take the content aka description field of the RSS feed and store it inside the “content” field on the wordpress side.

then Wordpress does it’s own thing, I have a plugin that save remote images back to the wordpress media folder and replace the remote link with the local one, do you think that could be the root cause of all this ?

I thought this was completely outside N8N and would not even get into the workflow :confused: