This message was deleted.

Unfortunately I don’t this there is currently any good way to diagnose where this came from. The error message here should be updated to have more context. Also - I believe we are already tracking a suggestion to do this type checking earlier so that it can be reported synchronously with the real call stack. Since the error mentions a tuple - I suspect the issue is an errant comma somewhere.