gitroomhq/postiz-app · error · BadBody

LinkedIn took too long to process the media, please try agai

Error message

LinkedIn took too long to process the media, please try again

What it means

LinkedIn media polling loop (waitForMediaReady style) exceeded 8 minutes without the asset reaching a ready state. It fails deliberately below the 10-minute Temporal activity timeout because a retried activity would re-upload and duplicate the publish; failing cleanly is safer than timing out.

Source

Thrown at libraries/nestjs-libraries/src/integrations/social/linkedin.provider.ts:1066

    const [response] = await this.postPending(
      id,
      accessToken,
      postDetails,
      integration,
      type
    );

    let pendingData = response.pendingData;
    const started = Date.now();

    // eslint-disable-next-line no-constant-condition
    while (true) {
      // Cap below the 10-minute activity timeout of the old workflows using
      // this method: failing here is safe (the post is only created once all
      // the media is ready), timing the activity out is not - a retried
      // activity would upload and publish again.
      if (Date.now() - started > 8 * 60 * 1000) {
        throw new BadBody(
          this.identifier,
          '{}',
          '{}',
          'LinkedIn took too long to process the media, please try again'
        );
      }

      const check = await this.checkPostStatus(
        accessToken,
        pendingData,
        integration
      );

      if (check.status === 'pending') {
        pendingData = check.pendingData;
        await timer(20000);
        continue;
      }

View on GitHub (pinned to 0f1647f749)

Solutions

Retry the whole post (safe: post is only created once all media is ready)
Reduce media size/duration so LinkedIn processes faster
If it recurs consistently, test the same asset via LinkedIn directly to rule out account/API throttling

Defensive patterns

Strategy: retry

Try / catch

if (/took too long to process the media/.test(err.message)) { /* safe to re-run whole post */ }

Prevention

Compress large videos before upload
Treat this failure as retry-safe: post not yet created

When it happens

Trigger: Polling LinkedIn's asset status endpoints for >8*60*1000 ms while processingStatus stays PROCESSING. Called from LinkedinProvider during post publishing when media is attached.

Common situations: Large videos, slow LinkedIn transcode queues, or assets stuck in PROCESSING. Network latency stretching the polling loop.

Related errors

AI-assisted analysis of gitroomhq/postiz-app@0f1647f749 (2026-08-27). Data as JSON: /api/errors/f9279ba832816e5b. Report an issue: GitHub.