(Glad ameade noticed this - I missed it) We don't want to hard-code what the valid actions are - you should be able to add new actions by just firing up workers that can handle them. At most a config tweak and restart to the api if overriding retry / timeout defaults for the new action. Qonos itself is action agnostic.

If we *do* want to let users know that an action can't be handled (which isn't a bad idea) we need to do it some other way - maybe workers need to register with the type of action(s) they can handle. The most I could see requiring would be to have every action have to be in the api config. But def. shouldn't need a redeploy to add new actions.