Schedule task stuck at waiting status
- Description of the issue: Schedule task stuck at waiting status
- Account name: Victorian Convention and Event Trust (MCEC)
- Region: APAC
- Client version: 25.22025080401
-
Steps to reproduce:
- Main menu > Schedule task > Added new > still in waiting status
- Go to Daily Revenue Job Configuration / Control, note the status is ‘Warning’
-
- Note that when user try to “Run Daily Revenue” message display as ‘The Job Control Record Type is not marked for Run.’
-
Please advice if this is a bug?
Observed results vs Expected results: Scheduled task should run with no error
- What is the job the client is trying to accomplish: Schedule task in dev environment
- Business impact if not resolved: HIGH
- Links to articles where you've looked for solutions and also other steps you've taken to research the issue:https://supportcenter.ungerboeck.com/hc/en-us/articles/204555938-Processing-Scheduled-Tasks
- Link to Zendesk ticket: https://ungerboeck.zendesk.com/agent/tickets/368859
- Local v30 URL:
- https://supportwebap.ungerboeck.com/MCEC_Dev_1700100308_USI_V30/app85.cshtml?ReturnUrl=%2fMCEC_Dev_1700100308_USI_V30#/scheduledTasks?data=fbda40735e51a54ca858dba52f7f64c4a443
- usiadmin/ITRocks2014
-
Hello Dustin Banks Please advice if this is a bug? Can we confirm if MCEC_Dev environment is configured for scheduled tasks?
-
Anitha Khairnar, it was setup but when it was upgraded to a new version from prod, the token was not updated. I have now updated this and its running successfully again.
-
Thanks Dustin. Will check with the customer.
-
Hello Dustin Banks Thanks for your help. It is resolved for the customer. But would like to know what do the warning status indicate? What actions do we need to take at that instance
-
Anitha Khairnar, I am not sure. This is a financials task. Ryan Ungerboeck, would you know what the status of Warning means?
-
Hey Dustin Banks - Just quick question from the customer to confirm if token is updated and running fine for other MCEC environments? Can you please confirm
25.12025081101 (PROD), 19.97C2021092601 (PRODHISTORICAL), 25.32025101301 (TEST), 24.12024102501 (TEST2)
-
Hello Dustin Banks
We may have request for copy from Prod later. So will this be an issue again with the token? Do we have any script in place to avoid this issue in other MCEC environments ? Please advise at the earliest. Thanks!
-
Once an environment is upgraded to the newest copy of prod, Ask your team lead to copy over the prod token to the upgraded environment setup. This only needs done on the first upgrade of that environment.
Please sign in to leave a comment.
Comments
8 comments
Date Votes