Agent is not available at specified time, eventhough he is!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2021 10:25 PM
Good morning.
I wonder if you guys have experienced this as well. I have a worker who I can't assign WOT to him. I get always the message "Agenti is not available at specified time" and "Invalid update", eventhough the worker has no other WOT or Event on that day. I've tried on different days and with Paris and Quebec. Always the same.
Does someone have a clou what this might cause?
Sincerely Daniel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-20-2022 02:37 PM - edited ‎10-20-2022 02:38 PM
Old post, but thought I would add that I noticed this same behavior today on a Tokyo demo instance.
Despite the error message, the root cause of the error in my case actually had nothing to do with agent schedules, which were set up correctly.
Rather, it seemed to be due to agent locations (sys_user.location) missing latitude and longitude values.
I observed that when using dynamic scheduling, specifically when using the "Matching Skills For Dynamic Scheduling " criterion in the Task filter (Field Service > Dynamic Scheduling Administration > Configuration > Your task filter), if any of the agents returned by dynamic scheduling have a "location" value with empty latitude/longitudes, it will throw this "no resources available" error.
Also, if any of the agents are missing a Location value altogether, I saw the same error.