Hi All, Thank you for your suggestions.
@Jon_Smith, @postwick our solution is build in RE framework. Due to architecture of solution planning, we haven’t used Orchestrator features in our logic other than scheduling the BOT. As @Anil_G & @ashokkarale mentioned the core concept of long-running activities, I tried with different approach to develop the solution without much changes in already developed code.
I customized the RE framework logic. Everything I shifted from End state ( where we had covered waiting and fetching updated data from AC ) to newly added parent scope in sequential order after RE Framework. All unnecessary variables scope set till RE Framework only. In following sequence we covered the logic to wait for all Action Center task & updated excel output. All variables scope limited to child sequence to void any issue for long-running activity.
Thank you again all !!! ![]()