So I dug a bit deeper into this. I tested using the same exact customizer on a very basic Web Services SaaS connector instance and my logs printed out just fine when tailing via the CLI. For the Workday SaaS connector, it seems to just be some sort of proxy which still uses the old school Java-based connector (hints in logs show of using Apache commons HTTP classes, etc.), so I guess customizers are not even invoked? This seems like a decent flaw to me. @developer_relations_team can we confirm this is the case that these customizers do not work for all ‘SaaS’ connectors?