@ancient-wolf-19325 I am getting error "ValueError: Received more input values 8 than allowed by the input spec 7" but from the input I can see I do have 8 in the specs

It seems likely that the error "ValueError: Received more input values 8 than allowed by the input spec 7" is related to a mismatch between the number of inputs provided and the number of inputs expected by the task or workflow. This error typically occurs when the number of inputs specified in the task or workflow definition does not match the number of inputs being passed during execution. My understanding is that you should verify the task or workflow definition to ensure that the number of inputs specified matches the number of inputs you are providing. Additionally, check if there are any default values or optional inputs that might be affecting the expected input count. Would you like more details on how to troubleshoot this issue? Sources: - Flyte GitHub Issue #2108 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 Which number is the expected?

It seems likely that the expected number of inputs is determined by the task or workflow's input interface as defined in its specification. The error message "ValueError: Received more input values 8 than allowed by the input spec 7" suggests that the task or workflow is expecting 7 inputs, but 8 inputs were provided. To resolve this, you should check the task or workflow definition to confirm the number of inputs it is designed to accept. This can typically be found in the Flyte task or workflow definition where the inputs are declared. Would you like more details on how to locate and verify this information in your Flyte setup? Sources: - https://github.com/flyteorg/flytekit/blob/master/flytekit/core/promise.py 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 Yes the inputs have been confirmed and I can see the number of inputs on the console and it's correct. Somehow I still get the error

If the inputs have been confirmed and the Flyte console shows the correct number of inputs, yet you still encounter the error, it might be due to a discrepancy between the input names or types in the task or workflow definition and those being provided during execution. Here are a few steps to troubleshoot further: 1. Check Input Names and Types: Ensure that the input names and types in your task or workflow definition match exactly with those being provided. Even a small mismatch can cause such errors. 2. Review Default and Optional Inputs: Verify if there are any default or optional inputs in the task or workflow definition that might not be accounted for during execution. These can affect the expected input count. 3. Inspect the Execution Context: Sometimes, the issue might be with how the inputs are being passed in the execution context. Ensure that the inputs are being correctly mapped to the task or workflow. 4. Check for Overridden Inputs: If there are any overridden inputs in the execution, ensure they are correctly specified and do not conflict with the expected inputs. Would you like more detailed guidance on any of these steps? Sources: - Flyte GitHub Issue #2108 - Flyte GitHub Issue #5270 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.