Jobs runs before time

[Ayzar Talip]

Hello partners!

Does anyone know why Jobs run ahead of schedule?

You know because the Jobs runs before time?

The job has configured to start at 18:30 hours and runs at 18:29:59

It happens to me with all the servers, although it is almost essential this causes me to run jobs ahead of time.

Did any of you have anything similar?

Thanks and regards!!

--------------------------------------

Hello partners!
Have any of you touched to see that the Jobs run before their scheduled time?

 

I have jobs on different servers that go ahead
I also have a task in automatic that synchronizes the schedules with the AD of all the servers

 

Has anything like this happened to you?

 

thanks and regards!!

--------------------------------------

Hola, compañeros!
Alguno de ustedes les a tocado ver que los Jobs corren antes de su tiempo programado?

tengo jobs en diferentes servidores que se adelantan
tambien tengo una tarea en automatico que sincroniza los horarios con el AD de todos los servidores

les ha pasado algo similar?

gracias y saludos!!

[Legacy User]

Hello

Does it always happen with this specific job scheduled to start at 18:30?

Is there any time synchronization server (NTP daemon) which changed the clock on the machine?

 

Regards

Jean Paul

[Lucy Zhang]

Hello,

 

Could you tell the product name for the scheduling manager?

 

Would suspect that there might be about one second off on the server's timestampt. If you can provide the agent receiver.log, we can check if there is any difference on the time when agent got the request and the time in the AFM.

 

Thank you,

 

Lucy

[Ravi Kiran Kunduri]

Hi,

 

Can you please check the system time where the servers , agent and Desktop Client (assuming you are using DE) are running. May be it will throw some light there.

[Ayzar Talip]

Hello, I have little with this product CAWA De R12
First some doubts
Why is a response correct?
Who is responsible for saying the correct answer?
What is the purpose of having a correct answer?

Responding to your questions
The product we have is CAWA Version 12
The schedule of all the servers is synchronized daily and automatically at 19:00 hours.
Most servers have the same regional settings and time and date formats, only some (Border with USA) have the different setting.
Overtaking so to speak does not happen at the same time or on the same server

Although it seems minimal the difference I have processes that can only send information in a very short period of time and if they send it sooner or later it is not received, the strange thing is that it is forward when it would normally be delayed by work load or by transit In the net.

Thanks and regards!!

 

 

*-*-*-*-*-*-*-*-*

Hola, tengo poco con este producto CAWA De R12

Primero unas dudas

Porque se marca como correcta una respuesta?

Quien es el responsable de decir cuál es la respuesta correcta?

Cuál es la finalidad de tener una respuesta correcta?

Respondiendo a sus cuestionamientos

El producto que tenemos es CAWA De versión 12

El horario de todos los servidores se sincroniza diario y de forma automática a las 19:00 horas.

La mayoría de los servidores tienen la misma configuración regional y formatos de hora y fecha, solo algunos (Frontera con USA) tienen el parámetro diferente.

El adelantamiento por decirlo de algún modo no ocurre a la misma hora ni en el mismo servidor

Aunque pareciera mínima la diferencia tengo procesos que solo pueden enviar información en un periodo muy corto de tiempo y si lo mandan antes o después no es recibido, lo extraño es que se adelante cuando lo normal sería que se retrasara por carga de trabajo o por tránsito en la red.

 Gracias por su tiempo!!

[Olusegun Oduntan]

Thank you for providing the product name and version. The possible cause is the time difference on the servers so will suggest to check the system time on all the servers; DE, Agent, and Desktop Client.

 

If further assistance is needed on this, please open a support case and provide a sample job information with server tracelog and agent’s receiver log.

 

Hope this helps.

[Lenn Thompson]

Good morning! Typically we want the person who asked the question to come back and say that the response was correct. But, in some instances we will mark an answer correct it if looks like a response worked. We do this so that if another user comes to the community and has the same question -- they can see the solution. 

 

If a question you asked was marked as answered but wasn't, just let me know and we can un-mark it as correct. easy to do

[keith.koehlert]

We have run into the same situation.  Support told us that the timers that look for work will pick up anything that is due NOW + 500ms.  In your case, it is likely that a timer fired after 18:29:59.500, which would result in your job running at 18:29:59.

 

This is apparently by design, so we are having to make modifications to our scheduling to account for this.