Events for error conditions can now be controlled more precisely, eliminating the need to manually set up failure paths. The emit failure event setting has been updated with three options:

• Always: Emit events for any logged error

• Never: Never emit events for logged errors

• Error response only (HTTP Request actions): Emit events for HTTP status code errors (404, 500, etc.) but not transient connection failures (timeouts, DNS errors)

This is especially useful for HTTP Request actions where you want to handle API response errors differently from network connectivity issues. Error response only is now the default behavior for HTTP Request actions. Existing actions that have emit_failure_event will have their their current behaviors preserved.