Jobs are somehow being cached with Horizon/supervisor

Hello

I have a really strange thing happening with my application that I am really struggling to debug and was wondering if anyone had any ideas or similar experiences.

I have an application running on Laravel v5.8 which is using Horizon to run the queued jobs on a Ubuntu 16.04 server. I have a feature that archives an account which is passed off to the queue.

I noticed that it didn't seem to be working, despite working locally and having had the tests passing for the feature.

My last attempt to debug was me commenting out the entire handle method and added Log::info('wtf?!'); to see if even that would work which it didn't, in fact it was still trying to run the commented out code. I decided to restart supervisor and tried again. At last I managed to get 'wtf?!' written to my logs.

I have since been unable to deploy my code without having to restart supervisor in order for it to recognise the 'new' code.

Does Horizon cache the jobs in anyway? I can't see anything in the documentation.

Has anyone experienced anything like this?

Any ideas on how I can stop having to restart supervisor everytime?

Thanks