A redesign example of reducing the size of a subJob

Below is a very simple Job with only one subJob, and the subJob has only three components. If this Job were to generate an error of the 65535 bytes limit during the build process, it would be an error with this Job's only subJob. You can try to reduce the number of components in that subJob.

The error might look something like this:

At least Job "HelloWorld" has a compile errors, please fix and export again. 
Error Line: 23424 
Detail Message: The code of method tRowGenerator_1Process() is exceeding the 65535 bytes limitCopy code to clipboard

Each subJob is named according to the first component that is used to start the subJob. The method name specified in the error message, tRowGenerator_1Process(), lets you know that the error is happening in the subJob that is started with the tRowGenerator_1Process() component. In this case, there is only one subJob in the Job, so it has to be this subJob that is the problem, but you can have more than one subJob.

You can break this subJob into two subJobs, one subJob with two components, and one with just one component.

Hopefully, making the problematic subJob smaller by breaking it down into two separate subJobs will resolve this issue.