You’re correct that publishing a Solution in Service Center can be used as a “bulk” way to refresh dependencies, but it’s important to understand when it behaves like a manual “Refresh All” in Service Studio and when it does not.

1. What a Solution publish actually does

When you publish a Solution in Service Center:

• All modules in that Solution are republished.
• During compilation, references are resolved against the currently published versions of their producers.
• For non‑breaking changes (e.g. internal logic changes, description changes, added optional logic, etc.), this is enough to bring consumers up to date and clear most TrueChange warnings. Refresh dependencies for multiple eSpaces
• The same applies if you publish the “Current Version” of a Solution that already exists. Refresh References Without Publishing in Service Studio

This is why publishing Solutions (for example an “All_Components” solution) is a common practice to republish the whole factory and refresh references in bulk. Refresh dependencies for multiple eSpaces

2. When it is not equivalent to “Refresh All” in Studio

The key difference is breaking changes in signatures:

• If you change:
  • Entity structure (add/remove attributes)
  • Action input/output parameters (name, type, mandatory/optional, etc.)
  • Public element names
• Then the consumer modules’ references must be explicitly refreshed in Service Studio (Manage Dependencies → Refresh All). Refresh dependencies for multiple eSpaces

In this scenario:

• Those references show up as red (not just yellow) in Service Studio.
• A Solution publish in Service Center won’t fix those red, broken references.
• You need to open each affected consumer (or use the Producer’s “Download All Consumers / Refresh All Open Consumers” pattern) and refresh dependencies in Studio. Automatically update dependancies

So:

• Yellow / non‑breaking changes → Solution publish is usually sufficient to bring consumers up to date. Most efficient way to bulk refresh dependencies and publish multiple modules?
• Red / breaking changes → You still need “Refresh All” in Service Studio on each affected consumer.

3. “Publish All Consumers” vs Solution publish vs Service Studio

From the articles you referenced:

1. Publish All Consumers (Service Center)

   • On a Producer’s page in Service Center, you can use Publish All Consumers.
   • This republishes all modules depending on that Producer. Most efficient way to bulk refresh dependencies and publish multiple modules?
   • Behavior is similar to a targeted Solution publish for that Producer + its consumers.

2. Service Studio bulk patterns

   • “Download All Consumers” + “Refresh All Open Consumers” in Studio:
     • Opens all consumer modules.
     • Lets you run a true dependency refresh operation across them. Automatically update dependancies
   • This pattern is what you must use for breaking change scenarios.

3. Solutions (Service Center)

   • Solutions can be used to:
     • Republish many modules or the entire factory.
     • Refresh non‑breaking references in bulk. Refresh dependencies for multiple eSpaces

4. Answering your exact questions

Does a Solution Publish effectively resolve all outdated references for the associated consumer modules without requiring manual intervention in Service Studio?

• For non‑breaking (yellow) outdated references: Yes, publishing a Solution usually brings consumers in line with the latest producer versions without opening each module in Studio. Most efficient way to bulk refresh dependencies and publish multiple modules?
• For breaking (red) changes: No, you must still open the consumers in Service Studio and perform a reference refresh.

Are Solution publish and manual “Refresh All” in Service Studio absolutely identical in goal and outcome?

• Goal: very similar (get consumers aligned with producer changes), but:
• Outcome:
  • Same for non‑breaking changes.
  • Different for breaking changes; only Studio “Refresh All” prompts you to fix broken references and adjust to changed signatures.

5. “Official” documentation / references

There isn’t a single official doc page that states “Solution Publish = Refresh All”, but the intended/official behavior is described and confirmed in several OutSystems forum answers by staff and MVPs:

• Solution publish auto‑refreshes references for .NET platforms when you publish the “Current Version” of a solution. Refresh References Without Publishing in Service Studio
• Solutions are officially recommended for:
  • Factory management
  • Bulk republish / refresh after updates or upgrades
  • Maintaining an “All_Components” solution for full‑factory republishing. Refresh dependencies for multiple eSpaces
• Split guidance between non‑breaking vs breaking changes (yellow vs red) is explicitly called out. Refresh dependencies for multiple eSpaces Most efficient way to bulk refresh dependencies and publish multiple modules? Automatically update dependancies

If you want a practical recommendation:

• Use Solution publish / Publish All Consumers as your primary bulk mechanism for safe, non‑breaking changes.
• For refactors that alter signatures, plan a controlled, manual dependency refresh in Service Studio for the impacted consumers.