Welcome to the new Box Support website. Check out all the details here on what’s changed.

Box Status

Box Toolkit Send Request Issue

Follow
New post
Dan Woerz

I've been using the Box Toolkit for a process that has worked for years with no issues.  Now, all of sudden we are getting "Read Timed out" after making call outs using Class.box.Toolkit.sendRequest.  It's strange because it's working fine in the  SalesForce sandbox.  So, it's only happening in production, recently.  

Thanks,

Dan

0

Comments

4 comments

Date Votes
  • Official comment
    Alex Novotny

    Are you getting an exception? Or any other information I can use to check for the error on the Box side? It looks like this blog post is tied to a free developer account... do you also have a production enterprise account with Box? 

    Thanks, 

    Alex, Box Developer Advocate

    Comment actions Permalink
  • Dan Woerz

    Thanks for the help. Like I said, it's been working for years flawlessly in SF Enterpise.  Testing and debugging is being done in the Sandbox and working like clock work.  My code is not the problem.  My code and the toolkit code are working bug free.   However, the thread is waiting for a response to read the data sent back, but for some reason it is timing out.  The failure is on the Box side.  Now, in the past I use to be able to open incidences with Box, so they could do a trace and give me feedback.  Maybe you know a way to still do this?

    0
    Comment actions Permalink
  • Darrin

    As a customer I probably can't speak to what Box Support can do to help.  If you open a case I am curious what you learn.  If you wouldn't mind sharing here I am always trying to get better.

    0
    Comment actions Permalink
  • Darrin

    Under the covers the toolkit (or SDK) is ultimately calling the REST endpoints at Box and as with all things internet, things happen with connections.  In our Apex we have retry logic that checks to see if we get a file Id back.  If not, it will retry the request, up to 3 times before finally logging an exception.  We find that we rarely fail 3 times.

    If you are finding it's failing every request, depending on your Salesforce experience you may be able to debug.  Since the Salesforce SDK is an unmanaged package, you could set up debug logs for the user executing the call, then use Visual Studio Code and the Replay Debugger to step through the code and see if you can find out which line is failing.

    -1
    Comment actions Permalink

Please sign in to leave a comment.