- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2020 08:35 AM
Hi, I am currently in the implementation of the Advanced Work Assignment for the sc_task, but the Capacity in use is not refreshing the counting after tasks are closed causing that Tech don't receive a new task.
Table: awa_agent_presence_capacity_list
Field: ac_workload
There's a Client Script (OOB) that run
function onChange(control, oldValue, newValue, isLoading, isTemplate) {
if (newValue < 0)
g_form.showErrorBox('max_capacity', getMessage('Capacity must be greater than or equal to 0'));
}
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2021 06:46 AM
Hi
Yes, I find the root of cause of the issue. There is a scheduled job called "Re-register AWA Record Watcher" which automatically re-create missing record watcher responders. It is active OOB and in my case it was set to false.
Make sure is set to true.
Let me know if this works for you.
Regards,
Edxavier Roberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2021 01:17 AM
Hello,
What was the condition ?
thanx in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2021 12:34 PM
This is a known error with ServiceNow.
If you are using 'Add Or Condition' in Service Channel anywhere, it would not free up the capacity.
We re-configured our service channels to not have 'Add or Condition'
PS: you can have regular 'Or' condition.
They did create a Problem ticket for this but no updates yet 😕
PRB1497434

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2022 01:10 AM
On my end the job is active and we do not have 'Add or Condition' in use but with some agents we also have this issue. Any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2022 07:15 AM
Can you share more about the use case, in what situations does the agent capacity not reset?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2022 10:57 PM
Hi kgag,
Out of about 50 agents working at the same time, only 2-3 agents have this at a time. But I have no idea exactly in which use case. At first I suspected this for agents who had time outs or rejected Work Items. However, the problem also exists with agents who have never worked with AWA before or are new and therefore have never had a time out or rejected a case. Unfortunately, it is really completely unclear to me why.