Troubleshooting

Symptom	Likely Cause
RuntimeException: Partner Directory service not available	Script not running in SAP CI runtime, or PD service is down
RuntimeException: Binary parameter not found...	Partner ID or Parameter ID mismatch — check spelling and case
Field not appearing in output	Rule target path may be wrong, or source value is null (null values are not written)
Conditional not matching	Check operator spelling, field path, and that the comparison value matches exactly (string comparison)
Wrong branch selected in conditional	Conditions are evaluated top-to-bottom; first match wins — reorder if needed
Orphan object in output (e.g. emails[0] = { type: "work" } with no value)	Constant or header rules are firing without their corresponding source field. Add a requires gate to the constant rules — see Conditional Execution with requires
Rule with requires never fires when expected	Field name typo in the gate, or wrong operator. Plain strings inside any/all are interpreted as exists; for value comparisons use the full { field, operator, value } form
Empty "any": [] rule never fires	An empty any array is treated as false (nothing to satisfy). Use all: [] if you actually want the rule to always run, or remove requires entirely

See also

• Mapping Rule Reference — rule properties and path syntax
• Setup — setup procedure