When you notice that there are Queue items, also verify if
they have been there for a long time without being processed ?
- The time of those
entries made
- If they have been
processed within 12 or 24 hours since the Queue item creation
- If they have not been processed,
verify if the trigger for that is enabled or disabled.
- If trigger is disabled,
find out why it is disabled – there may / may not be a reason for that
- If enabled, verify if
the jobs associated with that trigger have run or about to run
- If about to run, verify
when it’s time kicks in
- If already scheduled to
run, but not running – Verify if any previous job is struck making this go
to pending status
- If yes, see if the Jobs
that are keeping this pending are genuinely running and processing the
transactions associated with it’s Queue.
- If yes, look at the
volume and estimated time to finish the volume
- If no, see why it is
struck – verify logs . Try to figure out the root cause. If unknown,
please reach out.
- After the potential root
cause is identified – log a defect and create a backlog item
- Verify if the stuck job
can be killed without any impact
- Ensure the actual
scheduled job is running as expected and verify if the transactions are
being processed
- During the transactions
processing, verify if there are mixture of Success, Fail and Application
Exceptions.
- If exceptions counts are
noticeably high, verify if they are valid reasons.
- IF more application
exceptions or invalid reasons for exceptions – reach out or create backlog
item.
Notes to Self:
- Have the right to run the
jobs if number of pending jobs in Queue are high. – Should monitor if
queue items go in successfully if not stop the job.
- Check if all triggers
are enabled. If not, send an email out.
- Check if jobs are
faulted. If not let team know if Queue items are pending to be processed.
- If Application
Exceptions keep occurring to a bot stop the bot and let the team know. If
Any authentication with Salesforce or SimpliGov or ABBYY fails.
- Wish Disable trigger has
some notes feature on Orchestrator. Also, Any info. on historical (on and
off) as well as some SSO ID helpful for tracking.
- If bot is not processing transactions right, restarting might help.
- App Robot Number - X;
Get to know the robot names.
