Currently, scheduler failures due to API service call does not have clear error message in log. For example, registration returned with not enough capacity only shows JSON error in scheduler log. List failure with message being trunked is shows as JSON error with '{".
This is confusing and can delay development/testing.
Currently, scheduler failures due to API service call does not have clear error message in log. For example, registration returned with not enough capacity only shows JSON error in scheduler log. List failure with message being trunked is shows as JSON error with '{".
This is confusing and can delay development/testing.