Exception: Trying to pass a table-valued parameter with 13 column(s) where the corresponding user-defined table type requires 14 column(s).

[CodeRedick]

We're seeing this error in our logs after updating to 1.6.0. Luckily it doesn't actually seem to be breaking anything but I don't know if there's any side effects we haven't noticed yet.

Stack trace is attached.

SqlDurableTaskIssueStackTrace.json

[cgillum]

Hi @CodeRedick. The StackTrace.json file you shared doesn't include any error messages. Can you please share the error message?

[CodeRedick]

The error message is in the title of the issue, but here's a raw stack trace that's probably better anyway:

TaskOrchestrationDispatcher-2591660e646945419dd1b847e30fdc71-0: Unhandled exception with work item 'e399cb306cc6479f834e3296e85050b0': Microsoft.Data.SqlClient.SqlException (0x80131904): Trying to pass a table-valued parameter with 13 column(s) where the corresponding user-defined table type requires 14 column(s).
   at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
   at Microsoft.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader(Boolean isInternal, Boolean forDescribeParameterEncryption)
   at Microsoft.Data.SqlClient.SqlCommand.InternalEndExecuteNonQuery(IAsyncResult asyncResult, Boolean isInternal, String endMethod)
   at Microsoft.Data.SqlClient.SqlCommand.EndExecuteNonQueryInternal(IAsyncResult asyncResult)
   at Microsoft.Data.SqlClient.SqlCommand.EndExecuteNonQueryAsync(IAsyncResult asyncResult)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location ---
   at DurableTask.SqlServer.SqlUtils.WithRetry[T](DbCommand command, Func`2 executor, SprocExecutionContext context, LogHelper traceHelper, String instanceId, Int32 maxRetries) in /_/src/DurableTask.SqlServer/SqlUtils.cs:line 626
   at DurableTask.SqlServer.SqlUtils.WithRetry[T](DbCommand command, Func`2 executor, SprocExecutionContext context, LogHelper traceHelper, String instanceId, Int32 maxRetries) in /_/src/DurableTask.SqlServer/SqlUtils.cs:line 633
   at DurableTask.SqlServer.SqlUtils.ExecuteSprocAndTraceAsync[T](DbCommand command, LogHelper traceHelper, String instanceId, Func`2 executor) in /_/src/DurableTask.SqlServer/SqlUtils.cs:line 563
   at DurableTask.SqlServer.SqlOrchestrationService.CompleteTaskOrchestrationWorkItemAsync(TaskOrchestrationWorkItem workItem, OrchestrationRuntimeState newRuntimeState, IList`1 outboundMessages, IList`1 orchestratorMessages, IList`1 timerMessages, TaskMessage continuedAsNewMessage, OrchestrationState orchestrationState) in /_/src/DurableTask.SqlServer/SqlOrchestrationService.cs:line 387
   at DurableTask.Core.TaskOrchestrationDispatcher.OnProcessWorkItemAsync(TaskOrchestrationWorkItem workItem) in /_/src/DurableTask.Core/TaskOrchestrationDispatcher.cs:line 662
   at DurableTask.Core.TaskOrchestrationDispatcher.OnProcessWorkItemSessionAsync(TaskOrchestrationWorkItem workItem) in /_/src/DurableTask.Core/TaskOrchestrationDispatcher.cs:line 221
   at DurableTask.Core.WorkItemDispatcher`1.ProcessWorkItemAsync(WorkItemDispatcherContext context, Object workItemObj) in /_/src/DurableTask.Core/WorkItemDispatcher.cs:line 373
ClientConnectionId:590e79e5-aea7-47c2-b4bb-83f845d76f1a
Error Number:500,State:1,Class:16

Backing off for 1 seconds until 5 successful operations

[cgillum]

Oh, sorry, I totally missed that the error message was already in the title.

This seems pretty problematic. It suggests a mismatch between the code you're running and the database schema. I'm very surprised that you're not seeing any symptoms. My expectation is that orchestrations would get stuck because we can't successfully checkpoint their progress. At a minimum, I'd expect things to be running more slowly due to the backoff behavior ("Backing off for 1 seconds until 5 successful operations").