Getting "Invalid Y value for the connection block" in Robotics

General
, ,
1

When I tried to open the Automation getting “Invalid Y value for the connection block” in Robotics. If I tried to open by clicking “Yes”, all the connections were lost and most of the blocks are missing. Please find the attachment for the error screen shot.

The size of Automation file (.os file) is 2,208 kb & solution size is around 50 mb.

  • what could be the possible root cause & how to fix it?
  • what is recommended max, min size of .os file & solution file (a single Automation file & the whole solution)?

Please let me know if anyone encountered this error and how you resolved it. Thank you.

Sorry unable to upload the image.

2

Hello thanks for checking this out.

I found the cause & fix, it happened due to the size of the .os file & the way components are dragged & placed in automation. If you have any different theory on this issue please let me know.

There are two major points we need to note while developing:

  1. Keep an eye on the .os file size & its behavior, if you observe any slowness while developing use different automation for further development. After every major change(if you added at least 150 blocks) try closing the automation/Solution file & open it again, then only you can observe the slowness.
  2. And there is one more size attribute you need to look at, which is inside the .os file. Edit the automation file with notepad or notepad++, then under the “Automation Document” node you can find the size node. make sure value of X,Y is not greater than 20000,20000. If this this greater than suggested value, that means you have placed a block far down or right in automation. Please refer below snippet from os file.

By mistake if it is already more than suggested value, you are more likely to have this issue. So you need to modify all the Top, Left, X, Y Values of all connection blocks in that file or re-develop the code.

Snippet:

<OpenSpan.Automation.Automator Name=“Autx_P_PrepareFTPFiles” Id=“Automator-8DBF6A480217839”>




Note: You might lost some data(can’t give guarantee on this solution), you can recover at least 90-100% of it. Technically it should work & it worked for me.

Ultimate Solution: Create automation with less blocks/size. So you can avoid the above error.

Thank you.

3

@Rakshith Mende This is generally good practice. You want to keep your automations smaller in size for several reasons.

  1. They are easier to work on.
  2. They are easier to test since you can devise scenarios to reach every possible execution path if they are small enough.
  3. They make more sense when explaining what the purpose of the automation is.

I have seen some extremely large automations before without incident. I suspect in this case there is something else happening besides simply the size. I think you may be right about placing something extremely far off the screen. That may indeed be a bug although I have not experienced it before.

The takeaway is to keep your automations on one screen (i.e. you zoom to fit the entire automation on screen, and it should be legible from this view. If not, it is likely too large, and you might consider breaking it apart into smaller and more manageable pieces.