Skip to main content
Solved

204 response status may be treated as error


Valentin
Apprentice
Forum|alt.badge.img+1

Hello,

 

We are executing an external request to call a process flow in a custom component. The execution is successful and the process flow is completed, returning a 204 status.

 

 

  However, the toast / panel notifications displays this error.

 

Do you think this is because the 204 status (no response body content) is treated as an error? Can this be suppressed in any way? Thank you.

 

Best regards,

Valentin
 

 

Best answer by Dick van den Brink

Hi Valentin,

I don't think it is the 204 status code with no content.

In one of the requests there is probably a TSFMessages header with that error message.

You can read more about how you can convert those messages here:

OData API | Thinkwise Documentation

In the Indicium error log there should be more information why the error is shown. It might be because of an error in a process procedure or something.

Regards,

Dick 

 

View original
Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img+3

Hi Valentin,

I don't think it is the 204 status code with no content.

In one of the requests there is probably a TSFMessages header with that error message.

You can read more about how you can convert those messages here:

OData API | Thinkwise Documentation

In the Indicium error log there should be more information why the error is shown. It might be because of an error in a process procedure or something.

Regards,

Dick 

 


Valentin
Apprentice
Forum|alt.badge.img+1
  • Author
  • Apprentice
  • 9 replies
  • June 10, 2025

Hello,

 

Thank you for the response! The process step between the last action and “stop” was, for some reason, counted as missing in the error logs, even if the step was actually there. By including another process action in between that last action and “stop”, the issue seems to have resolved.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings