https://community.blueprism.com/t5/Product-Forum/Rumba-Mainframe-X-CLOCK-and-X-SYSTEM-Error-Messages/m-p/81612#M33164 Hi all, We are testing existing, stable processes in V6 as a prelude to upgrading from V4 to V6.  I've noticed a lot of processes using Rumba Mainframe (Walldata Office 2000 V6) are failing with the Exception "The execution of the function was inhibited because the target presentation space was busy, in X CLOCK state (X []), or in X SYSTEM state. Return code: (4)" or similar.  It appears most often between a read and write stage, where the Process would need to write a command into Rumba Mainframe (such as to move to subsequent pages) and then read what was on that page.  For example reading a note that had been left over multiple pages.  The amount of data to be read doesn't seem to be related as the error occurs when the process only has to read a single character or a large block of text. I have mitigated the problem slightly by introducing a 1 second wait between each write/read stage, but this isn't 100% successful.  In V4, these processes having been running Exception free for months. Does anyone have any suggestions to resolve this, short of re-developing all our Mainframe processes with longer and longer wait stages, as well as possibly re-attempt loops, until the processes are stable again? Thanks, Steve Wed, 24 Oct 2018 20:48:00 GMT StephenColeman 2018-10-24T20:48:00Z https://community.blueprism.com/t5/Product-Forum/Rumba-Mainframe-X-CLOCK-and-X-SYSTEM-Error-Messages/m-p/81612#M33164 Hi all, We are testing existing, stable processes in V6 as a prelude to upgrading from V4 to V6.  I've noticed a lot of processes using Rumba Mainframe (Walldata Office 2000 V6) are failing with the Exception "The execution of the function was inhibited because the target presentation space was busy, in X CLOCK state (X []), or in X SYSTEM state. Return code: (4)" or similar.  It appears most often between a read and write stage, where the Process would need to write a command into Rumba Mainframe (such as to move to subsequent pages) and then read what was on that page.  For example reading a note that had been left over multiple pages.  The amount of data to be read doesn't seem to be related as the error occurs when the process only has to read a single character or a large block of text. I have mitigated the problem slightly by introducing a 1 second wait between each write/read stage, but this isn't 100% successful.  In V4, these processes having been running Exception free for months. Does anyone have any suggestions to resolve this, short of re-developing all our Mainframe processes with longer and longer wait stages, as well as possibly re-attempt loops, until the processes are stable again? Thanks, Steve Wed, 24 Oct 2018 20:48:00 GMT https://community.blueprism.com/t5/Product-Forum/Rumba-Mainframe-X-CLOCK-and-X-SYSTEM-Error-Messages/m-p/81612#M33164 StephenColeman 2018-10-24T20:48:00Z