<#4248 [BUG] Don't drop stack traces> Issue create...
# flyte-github
a
#4248 [BUG] Don't drop stack traces Issue created by iirekm Describe the bug In
pyflyte run ...
I'm getting:
Copy code
Encountered error while executing workflow ...:
  Error encountered while executing 'train':
  isinstance() arg 2 must be a type, a tuple of types, or a union
Dropping stack traces from console logs is an anti-pattern, making debugging very hard. Ugly workaround (possible only on local machine): to `WorkflowBase.__call__`'s
except
block add:
Copy code
import traceback
            print(traceback.format_exc())
Flytekit version: 1.9.0 Expected behavior Full stack trace should be preserved. Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte