operators fail to get next case ID

Thanks Alex!

This also includes the addition of sorting cases by timezone (orders by latest time of day for respondent first)

:-))

As for sorting cases by timezone - might be very usefull, especially for countries with 11 timezones :-))

Yesterday I had the same problem.
There were cases available, but the operator got 'no case available'. When he logged in with another account he got cases again.. Could this be the same problem?

Since yesterday also cases that received an outcome (appointment) are not showing up in the operator performance charts...

Hello Joost,

Are you running the system sort process? If not, I would suggest you do. If
it was running - please confirm that it remained running as this can cause
this issue also.

Adam

On 25 November 2016 at 22:04, Joost <email address hidden> wrote:

> Yesterday I had the same problem.
> There were cases available, but the operator got 'no case available'. When
> he logged in with another account he got cases again.. Could this be the
> same problem?
>
> Since yesterday also cases that received an outcome (appointment) are
> not showing up in the operator performance charts...
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1468417
>
> Title:
> operators fail to get next case ID
>
> Status in queXS:
> Fix Released
>
> Bug description:
> It's an "old" problem for us: when new records from sample(s) are
> finishing or finished, system failes to get another case for
> operator, displaying "No cases available".
>
> Though in Admin panel there're "available cases" shown on
> outcomes.php and casestatus.php pages.
>
> Only assigning cases to exact operator @ casestatus.php (or temporary
> switching on "systemsort process") helped to get cases and continue
> work with the sample.
>
> Finally found the reason - function get_case_id (in
> functions.operator.php file) was not working properly, returned no
> case_id due to SQL querry error . Applying additional brakets in SQL
> querries helped to solve the issue.
>
> So far tested for 2 weeks, function is working good, all operator
> cases got as intended , no additional manupulation with case
> assignment or systemsort process required.
>
>
> Suppose it might be an issue with php /mysql config / versions /
> libraries ...
>
>
> Have a good queXS'ing,
>
> Good luck All,
>
> ALex
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/quexs/+bug/1468417/+subscriptions
>

--
Adam Zammit
Research and Development Officer, Survey Methodology
Australian Consortium for Social and Political Research Inc.
+61 3 9013 9653
http://www.acspri.org.au/

Hi,

I've done the updates you comment here in functions.operator.php and also the system sort process is running, but the answer of the process is:
126405 Wed 14 Nov 12:33AM Failed to complete sort. This task took: 0.016853809356689 seconds
126403 Wed 14 Nov 12:33AM Sorting cases for Prueba

I also have checked the cases and i get
"No hay caso disponible" - "No case available"

What do i have ti check?

Thanks in advance

Hi,

"Failed to complete sort" suggests there is something problematic not related to this bug.

One thing to check is if you selected a field in your sample filed to be a "token". If this token has been used in another survey in queXS it could clash. I would suggest loading the sample again without a token field.

Adam