Pega Loader Not Auto-Syncing Updates – Some Users Stuck on v25.1.1

General
1

Problem

We have a base install running Pega Loader v25.1.1, with v25.1.4 available on our sync server. However, some users’ Pega Loader instances are not automatically pulling and loading the newer version—they remain stuck on 25.1.1 despite the availability of 25.1.4.

What We’ve Already Verified

  • Confirmed affected users are not configured to load the runtime executable directly

  • Verified that manually triggering the download from Sync Server using the download/all command works successfully and retrieves version 25.1.4

The Question

What could explain why the Pega Loader fails to automatically pull down available updates for some users, even though:

  1. Their configuration appears correct?
  2. Manual downloads work without issues?

Additional Context

We’re planning to upgrade to v25.1.19 next, which would create an 18-iteration version gap from our current base install (25.1.1). We’re concerned this larger jump could amplify synchronization failures and introduce broader compatibility issues across more users. Understanding the root cause of the current automatic sync failure with v25.1.4 would help us mitigate risks for this larger upgrade.

Any insights or suggestions would be appreciated!

2

Hi Thierry, Could you please let us know how you triggered the download/all command and did you find any other fixes for the issue?

3

This is the command : http://localhost:5004/api/v1/download/all

We don’t have any other solutions so far. We might include a call to that URL directly in our automations. I’m also going to open a support ticket to get official Pega input.