Hi Outsystems Team,

I'm currently facing an issue where Service Actions do not receive the full set of client cookies, while Server Actions do.
This limitation prevents the use of HTTPRequestHandler.GetCookie / SetCookie inside Service Actions in real scenarios.

📌 Problem

When a request reaches a Screen Action or Server Action, all browser cookies are forwarded to the action's execution context.
However, when calling a Service Action, only a small subset of platform‑managed cookies (e.g., UserId, TenantId, etc.) is available.
This means:

• Custom cookies created by the application never reach the Service Action.
• HTTPRequestHandler inside a Service Action cannot read or modify these cookies.
• Some patterns related to authentication, tracking, and user context become difficult or impossible.

🔍 Expected Behavior

Ideally, a Service Action should be able to: 

1. Receive the same full cookie set that Server Actions receive.
2. Support HTTPRequestHandler.GetCookie and SetCookie.
3. Allow more advanced use cases such as: 
   • Authentication extensions
   • Cross-app user context sharing 
   • Tracking / analytics 
   • A/B testing 
   • Custom session or preference handling

🎯 Why This Matters

Many modern architectures rely on Service Actions as:

• Shared reusable service layers
• Abstraction layers across multiple applications
• Integration or cross‑module processing points
• Centralized logic for authentication, tracking, and user context

Without access to client cookies, these Service Actions become:

• Harder to design 
• Less reusable
• Less aligned with real-world requirements

This directly affects large-scale multi-app environments.

❓ Questions for OutSystems

1. Is there a recommended way to forward all cookies to a Service Actio
2. Is this a platform limitation or an intentional design restriction?
3. Is there any roadmap to allow Service Actions to access the full cookie context?
4. For now, we rely on a Server Action to read the cookies and pass them as input parameters. Is there a better official workaround?

💡 Additional Notes

• We do not need to modify platform-managed cookie.
• We only need to access custom cookies generated by the application.
• Everything works perfectly in Server Actions — the limitation occurs only at the Service Action layer.

🙏 Conclusion

I would like to propose a feature that allows Service Actions to:

• Receive all client cookies, or
• Optionally specify which custom cookies should be forwarded

This would make Service Actions far more flexible and suitable for real-world multi-application use cases.
Any insights, confirmations, or guidance from the community or OutSystems staff would be greatly appreciated.

Thanks in advance!