Server Version : 0.0.0.0 Studio Version : 0.0.0.0 Email Address : No Email Provided Steps to follow : No Steps Provided at Dev2.Studio.Core.UpdateProxy.SaveChatbotSource(IChatbotSource chatbotSource, Guid serverWorkspaceID) in C:\Builds\warewolf\Dev\Dev2.Studio.Core\UpdateProxy.cs:line 378 at Dev2.Studio.Core.StudioResourceUpdateManager.Save(IChatbotSource chatbotSource) in C:\Builds\warewolf\Dev\Dev2.Studio.Core\StudioResourceUpdateManager.cs:line 113 at Warewolf.Studio.ViewModels.ManageChatbotSourceModel.Save(IChatbotSource toSource) in C:\Builds\warewolf\Dev\Warewolf.Studio.ViewModels\ChatbotSourceModel.cs:line 111 at Warewolf.Studio.ViewModels.ChatbotSourceViewModel.Save(IChatbotSource source) in C:\Builds\warewolf\Dev\Warewolf.Studio.ViewModels\ChatbotSourceViewModel.cs:line 212 at Warewolf.Studio.ViewModels.ChatbotSourceViewModel.SaveConnection() in C:\Builds\warewolf\Dev\Warewolf.Studio.ViewModels\ChatbotSourceViewModel.cs:line 189 at Warewolf.Studio.ViewModels.ChatbotSourceViewModel.Save() in C:\Builds\warewolf\Dev\Warewolf.Studio.ViewModels\ChatbotSourceViewModel.cs:line 217 at Dev2.ViewModels.SourceViewModel`1.DoDeactivate(Boolean showMessage) in C:\Builds\warewolf\Dev\Dev2.Studio\ViewModels\SourceViewModel.cs:line 173 at Dev2.Studio.ViewModels.ShellViewModel.<>c__DisplayClass66_0.b__2(Object o) in C:\Builds\warewolf\Dev\Dev2.Studio\ViewModels\ShellViewModel.cs:line 271 at Dev2.Security.AuthorizeCommand`1.Execute(Object parameter) in C:\Builds\warewolf\Dev\Dev2.Studio.Core\Security\AuthorizeCommand.cs:line 106 at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated) at System.Windows.Controls.Primitives.ButtonBase.OnClick() at System.Windows.Controls.Button.OnClick() at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent) at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input) at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport) at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel) at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Warewolf Studio log file : at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent) at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input) at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport) at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel) at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) Warewolf Server log file : 2025-11-06 18:40:55,760 INFO - [Warewolf System Data] - Process Memory Usage(mb): 3 Number of Requests: 0 Time Taken(Ms): 0 Uptime: 00:17:04.6253306 Total Physical Memory: 15GB Total Available Physical Memory: 3GB Load Memory: 79% Used. 2025-11-06 18:41:21,773 INFO - [Warewolf Info] - Exiting with exitcode 0 [Footer]

Server Version : 2.8.13.18 Studio Version : 2.8.13.18 Email Address : bbuchan@theunlimited.co.za Steps to follow : This happened on studio start while trying to load the Start Page. No clicks, just opened the studio. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at MS.Internal.WpfWebRequestHelper.EndGetResponse(WebRequest request, IAsyncResult ar) at System.Windows.Navigation.NavigationService.HandleWebResponse(IAsyncResult ar) at System.Windows.Navigation.NavigationService.<>c__DisplayClass106_0.b__0(Object unused) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Warewolf Studio log file : 2025-11-05 09:25:51,240 INFO - [Warewolf Info] - Fail: The font family does not match. 2025-11-05 09:26:13,108 ERROR - [Warewolf Error] - Unhandled Exception System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 160.153.129.213:443 at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult) at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at MS.Internal.WpfWebRequestHelper.EndGetResponse(WebRequest request, IAsyncResult ar) at System.Windows.Navigation.NavigationService.HandleWebResponse(IAsyncResult ar) at System.Windows.Navigation.NavigationService.<>c__DisplayClass106_0.b__0(Object unused) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) 2025-11-05 09:26:13,124 ERROR - [Warewolf Error] - Unhandled Exception System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 160.153.129.213:443 Warewolf Server log file : 2025-11-05 09:25:49,606 DEBUG - [ad969820-cfb3-4be8-991f-fe5c4258ae43] - Getting container 2025-11-05 09:25:49,615 INFO - [Warewolf Info] - Fetch Duplicate ResourcesError 2025-11-05 09:25:50,629 DEBUG - [Warewolf Debug] - Execute Command Invoked For [ warewolf-new\dev2user : NTLM : True ] For Service [ FindSourcesByType ] 2025-11-05 09:25:50,631 DEBUG - [df6516f7-0ea8-499c-9bff-b875bbe8aa78] - Remote Invoke 2025-11-05 09:25:50,631 DEBUG - [df6516f7-0ea8-499c-9bff-b875bbe8aa78] - Mapping Inputs from Environment 2025-11-05 09:25:50,631 DEBUG - [df6516f7-0ea8-499c-9bff-b875bbe8aa78] - Creating Invoker 2025-11-05 09:25:50,632 DEBUG - [df6516f7-0ea8-499c-9bff-b875bbe8aa78] - Finding service 2025-11-05 09:25:50,632 DEBUG - [df6516f7-0ea8-499c-9bff-b875bbe8aa78] - Mapping Action Dependencies 2025-11-05 09:25:50,632 DEBUG - [df6516f7-0ea8-499c-9bff-b875bbe8aa78] - Getting container 2025-11-05 09:25:50,634 INFO - [Warewolf Info] - Find Sources By Type. Dev2Server

Given a large payload is returned

When Debug Output Reaches a maximum allowed characters

Then a “…” button is shown that allows, when clicked, to view the full payload.

Currently, this just errors when pressed.

I'm currently working on a service that requires setting a custom Accept header with the following value:

Accept: application/vnd.sasgtwy.v1+json

However, when I attempt to configure this in the HTTP Web Request tool within Warewolf, I receive the following message:

"The Accept header must be modified using the appropriate method or property parameter name: name"

It seems Warewolf expects the header to be set using a specific method or parameter, but it’s unclear how to apply this properly. I've tried adding it in the Headers section, but without success.

🔹 1. Web Request Tool — Parse Error on Binary Response

• When attempting to download a Genesys pre-signed audio file (MP3) via the Web Request tool, Warewolf throws a:

  nginxCopyEditparse error: { AudioFile }
  

• The tool does not provide any options to specify how the response should be handled (e.g., as text, binary, or base64). It attempts to parse the response automatically.

• 🧠 Root Cause: The tool likely assumes the response is text or structured data, and fails when encountering raw binary bytes from the audio stream.

🔹 2. GET Web Method Tool — Output Mapping Fails on File Response

• When using the GET Web Method tool to call the same audio file URL and clicking "Generate Outputs", the following error is shown:

  pgsqlCopyEditSpecified argument was out of the range of valid values.
  Parameter name: count
  

• Output mapping options (like assigning to object/recordset) are greyed out because the tool fails to test or build outputs from the binary response.

• 🧠 Root Cause: Since the endpoint returns raw binary (audio/mpeg), the tool cannot generate a data structure for mapping and gracefully disables output binding.

  Response when trying to test get api

While trying to connect to the third party's SFTP server through Warewolf, I encounter the following error. I am able to connect using FileZilla without any issues. I tried connecting to one of our internal SFTP servers through Warewolf to check if it was working, and it connected successfully.

It seems like the issue might be that the password is not supported by the Warewolf tool. Third party's SFTP password is 20 characters long and contains a comma and a backslash (special characters). While our internal SFTP password is 7 characters long and contains plus sign.

The current Docker image for the Warewolf application is based on Windows Server 2019 (ltsc2019) with the following characteristics:

• OS Version: 10.0.17763.6659

• Architecture: amd64

• Image Size (Uncompressed): ~7.06 GB

• Includes: Warewolf server, PowerShell-based entry point script

• Base Image: mcr.microsoft.com/windows/servercore:ltsc2019

Due to the use of the Windows Server 2019 servercore base image, the resulting image is relatively large. However, Windows Server 2022 introduces significant improvements that justify a migration:

 Benefits of Migrating to Windows Server 2022:

• Reduced base image size (~700 MB smaller)

• Faster container startup times

• Improved runtime and networking performance

Estimated Image Size Impact:

Layer/Component	WS 2019 Size	WS 2022 Size
servercore base layer	~3.47 GB	~2.76 GB
Warewolf + Additions	~3.5–4.0 GB	~3.0–3.5 GB
Total Image Size	~7.0 GB	~6.0 GB

Estimated reduction: ~1 GB or ~15–20% smaller overall image size.