Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
  • 1.  Problem with WOGEN Cron Task

    Posted Fri January 07, 2022 03:27 AM

    I just received the usual WOGEN e-mail listing the PM records that were evaluated tonight, and any work orders that were created.

     

    Two problems:

    1. The e-mail states that the work order generation started on Jan. 5 at 9:50 am, and finished at Jan. 5 at 9:52 am.  It was scheduled to run at 8:45 PM.  It therefore ran a BIT late.  Or a BIT early, depending on how you look at it. ��
    2. I received the e-mail on Jan. 6 at 10:48 pm.  So the e-mail is a BIT late too.

     

    Anyone got ideas? 

     

     

    TIA

     

    Shannon

     

     

     


    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: Problem with WOGEN Cron Task

    Posted Fri January 07, 2022 08:29 AM
    Without access to the system it's a bit tricky to triage. Can you look at the CRONTASKHISTORY table (viewable in the Cron Task application as well) and see what time it shows the PMWOGEN started and completed? That would be helpful to confirm when it actually ran. If the PMWOGEN is not set to keep history, you could look at the TASKCHEDULER table as well assuming it hasn't run again since.

    If it really completed on January 5 at 9:52 AM and you didn't receive the email until the next day, the issue can be difficult to triage. Maximo sends or loses the email immediately so it had to have sent it to the SMTP relay after completion of the PM WOGEN.

    Each organization manages outbound SMTP differently. For example, to ensure we didn't lose emails we configured a local SMTP relay that then forwarded on to an external delivery service. That way if the cloud service went down for some reason emails would get queued up locally. Others configure Maximo to hit an external delivery service (SendGrid, Office 365, GMail, etc.) directly. And some just use the local SMTP relay to send to the user.

    External email services have great visibility in to when the email was received by them and when it was sent on to the user but each manages it a bit differently. Sometimes you can useful information by viewing the Email Headers. Local SMTP typically does not have good visibility.

    There was an issue recently with Exchange (on-premises, not Office 365) where the new year was causing emails to queue up and not get sent. If a local Exchange environment is involved in your sending of emails, it's possible that there was a large backlog of emails and that would explain why it took so long to send. The post about the issue can be found here: https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-exchange-on-premises-transport-queues/ba-p/3049447

    ------------------------------
    Steven Shull
    ------------------------------



  • 3.  RE: Problem with WOGEN Cron Task

    Posted Fri January 07, 2022 06:43 PM

    Hi Steven:  thanks – will take a look into the CronTaskHistory.

     

    This actually is not a one-time event.  It's been happening for at least a year.  It should have been looked at before, but there were too many other priorities on the plate.

     

    I'll talk to the e-mail guys too.

     

    Thanks again

     

     

     

     






  • 4.  RE: Problem with WOGEN Cron Task

    Posted Sat January 08, 2022 09:18 AM
    There have been a few APARs related to poor performance of the PM WOGEN. Are you running for multiple sites and only looking at the email from a single site? It's possible an earlier site is taking a long time to generate. The cron task history would help identify that scenario since it has only a single start/stop time. If that's the case let me know and I can send you some of the APAR #s. 

    If it's reoccurring and your instance isn't in maintenance during that time and it doesn't seem related to the PMWOGEN of another site, I'd probably open a support case.​

    ------------------------------
    Steven Shull
    ------------------------------



  • 5.  RE: Problem with WOGEN Cron Task

    Posted Sun January 09, 2022 03:06 PM
    Hi Shannon, for the difference of 1 hours, it might be related to server versus client PC timezone. For the 1 day difference, I have no ideas.

    ------------------------------
    Mauricio Poblete
    ------------------------------