Announcements
@SM-31031325-0,
The given response usually indicates that the connector is receiving an empty or null response, or the response content is not being properly parsed or formatted. Can you please check the following areas?
Here are some key points and troubleshooting tips to resolve this:
Check Content-Type and Encoding: Let's make sure that the API response’s Content-Type header matches what your connector expects (e.g., application/json). Mismatched encoding or content types can cause parsing errors.
Content-Type
application/json
Handle Empty or Null Responses: Some APIs return empty bodies or null characters (\u0000) in certain cases. Add validation or default handling in your connector or downstream flow to manage such cases gracefully.
\u0000
Update or Re-import the Connector: Sometimes re-importing or updating the connector definition can resolve schema or caching issues.
Check the API Response: Verify that the backend API or service your custom connector calls is returning a valid, non-empty response. Use tools like Postman or curl to test the API endpoint directly and confirm the response content and format.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 377
11manish 279
David_MA 234 Super User 2026 Season 1
