This topic was automatically generated from Slack. You can find the original thread here.
I’m having problems testing my Go code step. It’s caching my previous code (printing “test”) and when I update my code it is still just printing “test”. Is there anything I can do to wipe the cache?
The only fix I have found is to publish my project, which will run the updated code and throw an error if there is any, then go back and edit it. Any advice would be greatly appreciated
When you go back and edit it after deploying your workflow (is this what you mean as publishing your project?), it rolls back to the previous code?
My changes are saving. However, when I try to test my code, it is testing a previous version. It has “cached” my code when it comes time to test. To test my changes, I have to click “Publish”, then “Edit” to go back to my code step, then I can test my code.
Oh maybe you have to select a new event from the trigger in the edit mode?
I’m using the same event/trigger in the first step, but I’m making changes to the second step (running Go code). I got an error (nil pointer dereference). I fixed the error, but when I go to test, it’s still running my old code that panics with the same error. I can’t publish it now to clear the “cache” so now I can’t make changes
Got it, I’ll try to repro this asap!