From 2cd90ad01120d473ae5a2a36c01a39f17a7a2158 Mon Sep 17 00:00:00 2001
From: Sipke Schoorstra <sipkeschoorstra@outlook.com>
Date: Thu, 12 Dec 2024 23:08:48 +0100
Subject: [PATCH] Fix logging to display full variable type on parse failure

Updated the log message to use the full variable type name instead of the base type. This provides more detailed context for debugging failed variable parsing issues.
---
 .../Elsa.Workflows.Core/Services/VariablePersistenceManager.cs  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/modules/Elsa.Workflows.Core/Services/VariablePersistenceManager.cs b/src/modules/Elsa.Workflows.Core/Services/VariablePersistenceManager.cs
index 443acd0a7..663e0057d 100644
--- a/src/modules/Elsa.Workflows.Core/Services/VariablePersistenceManager.cs
+++ b/src/modules/Elsa.Workflows.Core/Services/VariablePersistenceManager.cs
@@ -47,7 +47,7 @@ public class VariablePersistenceManager(IStorageDriverManager storageDriverManag
 
                 if (!variable.TryParseValue(value, out var parsedValue))
                 {
-                    logger.LogWarning("Failed to parse value for variable {VariableId} of type {VariableType} with value {Value}", variable.Id, variable.GetType().Name, value);
+                    logger.LogWarning("Failed to parse value for variable {VariableId} of type {VariableType} with value {Value}", variable.Id, variable.GetVariableType().FullName, value);
                     continue;
                 }