Hello Santosh,

I'm not sure I follow. Are you saying that you have a flowaction, which is designed to submit itself onLoad? And occasionally you get transaction ID mismatch issues? Have you used Fiddler or a similar debugger to see exactly where your transaction IDs go wrong? I'd probably start there. If I had to guess, you are passing a transaction boundary and not refreshing a critical section which leads to it using stale data when it autosubmits. Once you figure out which section needs to be refreshed, you probably just need to make sure that happens before you call the action which calls the commit.

Thanks,

Mike

>>> Are you saying that you have a flowaction, which is designed to submit itself onLoad?

It's an out-of-the-box one.  Here's the out-of-box ActionAutoSubmit that it uses.  I notice this is "IE only" by the way !  /Eric

<SCRIPT>

<%

String strMessages = tools.getPrimaryPage().getMessagesAll();

  if(strMessages.length() == 0)

  {

   tools.appendString("if(window.name != null && typeof(window.name) != \"undefined\" && window.name == \"actionIFrame\" ){");

           tools.appendString("pega.util.Event.addListener(window,\"load\",doSubmit);");

   tools.appendString("}else{");

   /* BUG-168564: Updated doSubmit to call after loading all files. */

   tools.appendString("pega.u.d.attachOnload(doSubmit);}");

  }

%>

</SCRIPT>

I think Mike's idea of using fiddler to see where the transaction id is changing is a good one.  Are you still having this issue ?  /Eric