/joc/api/order endpoint provides no information on newly added orders

Current Situation

• When an order is added then no information is returned by the /joc/api/order endpoint. This happens if the endpoint is called immediately after the order was added.
• At the same time the order is visible from the GUI that makes use of the /joc/api/orders endpoint.

Desired Behavior

The /joc/api/order endpoint should return order information with its response as soon as an order is added.

How to reproduce

Workflow W1 starts with job J1 which makes use of the endpoint /joc/api/order for the order ID O1. When job J1 starts and calls the /joc/api/order endpoint then the following exception is raised:

ControllerObjectNotExistException

Workaround

Add a dummy job as the first job in the workflow that implements a delay of 5s.

Maintainer Note

• JS7 products are operated asynchronously. There cannot be a guarantee for an immediate response.
• In the underlying situation the order is added to the Controller, but is requested from the Proxy Service when checking the order's existence. There can be slight delays until the information becomes available in the Proxy Service.
• The /order API performs fewer tasks than the /orders API which suggests that the latter API request more probably will return a response about a recently added order for the simple reason that it takes more time. However, an immediate response about existence of an order is not guaranteed from the /order API and not from the /orders API.