Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
28-07-21 07:07 AM
I am using Utility HTTP VBO multipart request for Posting .xlsx file
It is working fine with Smaller size but throwing below error with bigger file size (34 MB)
Error :
Could not execute code stage because exception thrown by code stage: Object reference not set to an instance of an object.
When I remove the Try catch block , it shows below error
Could not execute code stage because exception thrown by code stage: The operation Timed out
Hence I assume this is related to timeout. It takes around 2 min 10 seconds before it throws error.
Also it is working from POSTMAN hence nothing wrong from API side
Is there anything needs to be done to increase timeout limit from Blueprism or is there any other issue ?
Please assist.
------------------------------
Kirtish Trivedi
------------------------------
It is working fine with Smaller size but throwing below error with bigger file size (34 MB)
Error :
Could not execute code stage because exception thrown by code stage: Object reference not set to an instance of an object.
When I remove the Try catch block , it shows below error
Could not execute code stage because exception thrown by code stage: The operation Timed out
Hence I assume this is related to timeout. It takes around 2 min 10 seconds before it throws error.
Also it is working from POSTMAN hence nothing wrong from API side
Is there anything needs to be done to increase timeout limit from Blueprism or is there any other issue ?
Please assist.
------------------------------
Kirtish Trivedi
------------------------------
Answered! Go to Answer.
1 BEST ANSWER
Helpful Answers
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
28-07-21 10:16 AM
Hi @Kirtish Trivedi,
Since the file size is quite huge and the default timeout of httpWebRequest is 100s (100,000 ms) hence increasing the timeout value should resolve the issue. Please try the below approach by going to "HTTP Request" action of "Utility-HTTP". (I am assuming that you are using HTTP Request action stage only). Add the Timeout property in the code stage and it should resolve the issue.
Note - 400,000 means 400s. It can be configured based on the requirement.
------------------------------
Ritansh Jatwani Senior Consultant
Consultant
EY
Gurgaon
*If you find this post helpful mark it as best answer
------------------------------
Since the file size is quite huge and the default timeout of httpWebRequest is 100s (100,000 ms) hence increasing the timeout value should resolve the issue. Please try the below approach by going to "HTTP Request" action of "Utility-HTTP". (I am assuming that you are using HTTP Request action stage only). Add the Timeout property in the code stage and it should resolve the issue.
Note - 400,000 means 400s. It can be configured based on the requirement.
------------------------------
Ritansh Jatwani Senior Consultant
Consultant
EY
Gurgaon
*If you find this post helpful mark it as best answer
------------------------------
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
28-07-21 10:16 AM
Hi @Kirtish Trivedi,
Since the file size is quite huge and the default timeout of httpWebRequest is 100s (100,000 ms) hence increasing the timeout value should resolve the issue. Please try the below approach by going to "HTTP Request" action of "Utility-HTTP". (I am assuming that you are using HTTP Request action stage only). Add the Timeout property in the code stage and it should resolve the issue.
Note - 400,000 means 400s. It can be configured based on the requirement.
------------------------------
Ritansh Jatwani Senior Consultant
Consultant
EY
Gurgaon
*If you find this post helpful mark it as best answer
------------------------------
Since the file size is quite huge and the default timeout of httpWebRequest is 100s (100,000 ms) hence increasing the timeout value should resolve the issue. Please try the below approach by going to "HTTP Request" action of "Utility-HTTP". (I am assuming that you are using HTTP Request action stage only). Add the Timeout property in the code stage and it should resolve the issue.
Note - 400,000 means 400s. It can be configured based on the requirement.
------------------------------
Ritansh Jatwani Senior Consultant
Consultant
EY
Gurgaon
*If you find this post helpful mark it as best answer
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
28-07-21 10:21 AM
Thank you @ritansh.jatwani
------------------------------
Kirtish Trivedi
------------------------------
------------------------------
Kirtish Trivedi
------------------------------