Hi,
We have few workflow configured and its working for past one year. suddenly its not working from yesterday.
Workflow have source account update/create as trigger and “HTTP request” as action.
Getting error as “http: Request.ContentLength=311 with nil Body”
I have verified the endpoints used are active and working as expected outside IDN
Hi @Manju22 have you tried http request using postman or curl? May be endpoint signature has changed. Another thing I should try is to remove http request action and recreate it from scratch. Some times I can fix workflows errors that way.
Hi @Manju22 ,
Since you say the endpoints are verified outside IDN, here are my initial thoughts.
Reading about the error tells me that the expected body length is 311 bytes, but what is being sent is 0.
This could be a data issue. Maybe searching for nil values of the SnowflakeStudyTeam will reveal empty values while the HTTP header is set to expect a text of 311 bytes.
Next is to try what Julian mentioned.
If that does not fix/ you do not intend to do that then
Look into the possibility of getting the workflow logs, look for lines similar to the error, and see how these logs(messages) worked when the workflow worked fine.
Thank you
Thank you. I have tried recreating the workflow, still it fails with same error.
I could see requestbody has value from the execution history.
Curious to know if you have a solution. Please share if you got it
Thank you
We’ve seen this too.
It’s mind boggling why it’s even a thing from a supposedly leading product in the IGA space.
I submitted a support ticket but I haven’t received a solution yet.
In my case (this was about 3 months or so ago), we had to recreate the HTTP action step. The actual root cause is still unknown, but we suspect it had something related to how the step references the credential is called / used / related in the backend. This may / may not be the same issue that the OP is facing.
Are you able to resolve the issue?
@Manju22 is the workflow working fine in sandbox. if yes you can check in log what value its showing compared to prod.
No. Its not working in dev and PROD. Same error.
ok… if it was working before and stopped working without making any change from sailpoint then I believe something got updates from system with which your application is integrated
Is request content type of Text the expected type? When SailPoint added the ability to adjust this - these defaulted to Text - that broke some workflows. You may need to recreate the action or adjust it to send something like JSON.
