HTTP Request Error

[ezninnovation]

I started getting this error. I have stripped all variable data out of the URL for testing and just making a static call that works in Postman but is failing with this error in Switch.

Cannot read properties of undefined (reading 'status') TypeError: Cannot read properties of undefined (reading 'status') at a0_0x40c41b.processCurrentJob


Rest of the error here:

(C:\Users\switch\AppData\Roaming\Enfocus\SwitchProcessorService\cache\7f1ff3b80ea955a15d57c6797ae61f06e7c430c8ab16327ec2ca2029c1515c7e\1746771349\main.js:1:27175) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async a0_0x40c41b.perform (C:\Users\switch\AppData\Roaming\Enfocus\SwitchProcessorService\cache\7f1ff3b80ea955a15d57c6797ae61f06e7c430c8ab16327ec2ca2029c1515c7e\1746771349\main.js:1:21278) at async jobArrived (C:\Users\switch\AppData\Roaming\Enfocus\SwitchProcessorService\cache\7f1ff3b80ea955a15d57c6797ae61f06e7c430c8ab16327ec2ca2029c1515c7e\1746771349\main.js:1:20995) at async _0x200e34 (C:\Program Files\Enfocus\Enfocus Switch\ScriptExecutor\nodemodules\node_modules\switch-scripting\index.js28) at async C:\Users\switch\AppData\Roaming\Enfocus\SwitchProcessorService\cache\7f1ff3b80ea955a15d57c6797ae61f06e7c430c8ab16327ec2ca2029c1515c7e\1746771349\main.js:1:71638

[Malcolm Mackenzie]

a bug in 20.4 of the app

[ezninnovation]

Any suggestions or workarounds? Do I need to go back to 20.3?

[ezninnovation]

a bug in 20.4 of the app

Any suggestions or workarounds? Do I need to go back to 20.3?

[Malcolm Mackenzie]

Yes reverting should be good.

[ezninnovation]

Seems like a double edge sword. With 20.3 I have basic authentication issues but with 20.4 I have the other error. Hopefully this gets addressed soon.

[rocky07]

This error usually means the HTTP Request app in Enfocus Switch isn’t receiving a proper response object from the server, so when it tries to read the `status` property, it fails because it’s undefined. Even though the URL works fine in Postman, Switch may be blocking or mishandling the response due to missing headers, authentication, or an invalid response format. Double-check that your request method, headers, and SSL settings match your Postman setup. Also, wrap your response handling in a try/catch block or add a response check before accessing `response.status` to avoid the crash.