Forum Discussion
Matthias
3 years agoNew Contributor III
We’re seeing the same behavior, pipelines that have been running for several months without major issues are now having the same exact error you’re also seeing.
We’ve quite recently updated this particular snaplex to 4.31 GA - and we didn’t really see this same error before that, so maybe it’s related to this?
Are you also on 4.31 GA?
did you get in touch with support yet? or maybe you found a solution (or cause) already?