What about having the Push in one active link then the rest of the actions in the next AL with a higher execution order. I am not sure if this will get around the timeout though. Another option would be to put the push in one AL and the other actions in an AL guide, then call the Guide after the push finishes. Again, this will need to be tested to see if it gets around the timeout.
On Mar 5, 2:44 pm, LJ Longwing <[email protected]> wrote: > Quick question (hopefully) > > ARS 7.1 Server and Mid-Tier > > I have a button press that causes a push to happen. This push can sometimes > take in upwards of 5-8 min's to happen, later actions in the AL fail to fire > because of client timeout. The timeout window seems to be about 2 min's > give or take a few secs....I'm trying to either extend the timeout, or find > a way to reattach the client to a server side process once it finishes. I'm > considering moving the entire thing server side and just sending the user an > email when it's done...but that's not desired. Any suggestions?...oh...and > I've troubleshot the process...it's not taking too long in any 1 > point...it's just an extensive process...it's all internal to > remedy...copying records from location a to location b when needed...but > there can sometimes be 10-20 thousand records that need to be copied...which > just takes a bit of time. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
