Skip to main content

Hi All.

In Customer Order functionality, whenever we change status (example: Planned to Released), it doesn’t change status immediately. We have to refresh windows multiple times then check background job etc. it changes after sometime. It happens not only in Customer Order window but also in other windows like Delivery etc.

Do you guys also face this issue. Please guide what could be the reason behind this.

Note: We have faced this issue mostly with Customer Order Functionality, other modules process fast.

 

Regards

 

 

Hi,

Have you configured batch queues?

The status change will never be immediate since the process does a lot of checks and initiation of extra processes which may result in information being fed back to the form.

However, if you change the default batch queue of background jobs the you can reduce bottle necks in background job queues.

See attached picture.

Regards,
Antony

Hi Mirali,

You can use “Online Processing”.

 

@anbouk We haven’t configured batch queries. Will look into it.

Thanks.

@sefer.ercan I am aware about that feature but the problem with it is, it doesn’t allow to switch windows while processing. Otherwise its fine.

Factors in addition to the aforementioned reasons that can affect the release cycle or status change:

  • Configured items on order
  • Project connected items on order
  • Intersite connected item on order
  • Number of lines on order is exceptionally long (more than 10 or so and the release time becomes noticeable)

Analyzing the other background jobs that are occurring within the time period or the number of orders being processed simultaneously may also give clues where to locate the bottle neck.

@ShawnBerk Thanks.

 

Reply


Terms & ConditionsCookie settings