Sub workflow notes

1. Why does a child workflow need to start with an "End Jump (1)" and end with a "Start Jump (2)"?
Is there any specific logic behind how Adobe handles this in the back end?

- This is how it is made to work by Product. There is no additional reason behind this

2. If I save my sub-workflow and call it in my primary workflow, will the sub-workflow execute every time?
I want to ensure that fresh data is used, as my sub-workflow contains a query that retrieves data from the customer schema, which is updated daily.

- Yes, it will work everything as long as the Sub-Workflow query is executed in the main workflow. Would it pick the latest data? It depends on how the workflow is configured

3. If an error occurs, a copy of the sub-workflow is created for debugging.
In such cases, do I need to call the copy of the sub-workflow in my primary workflow (e.g., copyTest instead of test)?

- No, there is no need to update the Primary workflow with the copy. The new copied workflow is purely for dubugging

4. In my primary workflow, can I call the sub-workflow directly after the Start activity?
Will it work? If not, what conditions or configurations should I take care of before and after the Sub-Workflow activity in the primary workflow?

- Yes, You should be able to call Sub-workflow activity no additional configuration is required.