We norticed that 4 of outr replication packages were stuck in a queued state since 9/14. Once we recognized the issue, I cancelled the run and am in the process of trying to re-execute. One example is run id: 106260600. I've never observed this before. We got no notification. Any clue?
Thanks,
Mort
It appears that all 4 packages are now stuck in the canceling state. I am unable to kick off a new run while they are in this stuck condition. The 4 run ids are: 106260600, 106206747, 106206748, 106206749. Can you kill these processes and enable the scheduled package runs to resume. This is impacting production reporting and has been out of service for over a week.
Thanks,
Mort
Hello Mort,
Sorry for the inconvenience with this. There was an issue on our side, and we have fixed it.
Unfortunately, notifications are not sent in cases of queued, canceling states. We will consider the possibility to improve this for users' convenience.
We have canceled these packages.
Best regards,
Mariia
All appears to be resolved. The packages are now back on scehdule and have all run successfully.
My one request is that you improve reporting on "stuck in queue" runs.
Thanks,
Mort
Hello Mort,
Thank you for your reply.
We will definitely consider improving reporting for queued packages.
If we can assist you any further, feel free to contact us.
