ServicePulse StackTrace view truncates the beginning of the exception text

[YDEdi]

Describe the bug

Description

When viewing some failed messages in ServicePulse, the StackTrace tab does not display the beginning of the exception text correctly.

The same failed message contains the full exception message and stack trace when retrieved from the ServiceControl API, and the Export message action also contains the full content.

So this looks like a UI rendering issue in ServicePulse rather than a backend/API issue.

Expected behavior

The StackTrace tab should display the full exception text from the beginning, exactly as returned by the API / export.

Actual behavior

The beginning of the exception text is missing in the StackTrace tab.

Versions

ServicePulse v2.6.0 - Service Control: v6.13.0

Steps to reproduce

Relevant log output

Additional Information

{"id":"a7ce6ba4-3327-065f-9527-a0607c8a0892","message_type":"Edisys.DIE3.Archiver.Contracts.Commands.CleanProdsysDirectoriesCommand","time_sent":"2026-03-19T01:00:01.299484Z","is_system_message":false,"exception":{"exception_type":"System.Data.SqlClient.SqlException","message":"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)","source":".Net SqlClient Data Provider","stack_trace":"System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): Le chemin réseau n’a pas été trouvé\n   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)\n   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)\n   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)\n   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)\n   at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)\n   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)\n   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)\n   at System.Data.SqlClient.SqlConnection.Open()\n (...)

what is exported when "Export Message" button is clicked :

STACKTRACE
System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): Le chemin réseau n’a pas été trouvé
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
...

[saratry]

@YDEdi Thank you for reporting the bug. Please follow this issue for updates on its resolution.

[dvdstelt]

Hi @YDEdi,

Thanks again for reporting this, really appreciated!

We’ve put together a fix (see PR #2919) that's currently under review. Even after it's merged, we can't provide a clear timeline for when it will be included in a release.

The good news is that the issue is inconvenient but not harmful, and as you mentioned, there are workable alternatives in the meantime.

We'll make sure it's included in a future release, though we don't have a specific ETA for now.

Thanks for your patience!