@forge/realtime throws exception in publishGlobal

Forge
1

Hello,

We’re facing sporadic exception when using @forge/realtime.

SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
at JSON.parse (<anonymous>)
at _ (/mnt/wrapper/wrapper_v22_85.cjs:2:1301355)
at o (/mnt/wrapper/wrapper_v22_85.cjs:2:1301121)
at fullyReadBody (/mnt/wrapper/wrapper_v22_85.cjs:2:895317)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async b (/mnt/wrapper/wrapper_v22_85.cjs:2:1301204)
at async publishGlobal (webpack://OUR_APP/node_modules/.pnpm/@forge+realtime@0.3.0/node_modules/@forge/realtime/out/publish.js:110:1)
at async OurService.queueEventListener (webpack://OUR_APP/src/OurService.ts:58:7)
at async Object.cardContentQueueHandler (webpack://OUR_APP/src/OurHandler.ts:27:10)
at async /mnt/wrapper/wrapper_v22_85.cjs:2:1276411

The content we’re trying to publish is a valid JSON string.

Is there a limit on the payload size ? This failing one is about ~18Kb

Can someone shed lights on this ?

:folded_hands:

2

Hi @GuillaumeBero, I had a look, and I believe this issue was caused by our backend systems not handling the recent uptake of Forge realtime traffic well.

I’ve adjusted our scaling rules, and our monitoring indicates that the errors have decreased. Are you still encountering these errors now?

3

Many thanks, will keep you posted if it happens again, but it was rather frequent.

4

Hey @GuillaumeBero , just circling back on this, we’ve made some adjustments again on our backend systems to improve the reliability of Forge realtime.

From our monitoring, the number of errors have significantly reduced, this should hopefully mean that these errors aren’t popping up for you anymore.

5

Hello @BoZhang was also trying out the forge/realtime publishGlobal however we are also encountering irregular errors same as @GuillaumeBero error.

JSON that being sent in our plugin only composed of issuekey and some id parameters. Has forge/realtime been improved recently regarding these errors?

6

@PaulReal since May 7, 2026 06:37:04 UTC we’re also seeing issues in @forge/realtime across our instances.

Unexpected token 'u', "upstream c"... is not valid JSON

This is not always reproducible, but has severe impact on our products.

Did you raise a Forge ECOHELP for it ?

7

Hi @PaulReal @GuillaumeBero , the team have been notified and are currently looking into this. Sorry about the inconvenience.

8

We didn’t get any error reports between 7:45 and 13:47 UTC, but the issue is active again unfortunately.

9

Hey @GuillaumeBero , really sorry about this.

We’ve been monitoring this issue over the past couple of days and have implemented mitigations to prevent it from impacting capability. Based on our metrics, there shouldn’t have been any occurrences over the last couple of days (since the 12th of May). Please let me know if this isn’t the case.