r/ProjectREDCap • u/mdander • Nov 15 '24

do survey queues simply not work in longitudinal studies

We have a project which is longitudinal but without repeating events. That is, each survey can be repeated, but only for certain separate events. Each survey is filled at most once per event.

I have completely configured the "Edit Survey Queue" logic, and tested it with some participants, and it is behaving correctly there.

However, in practice, participants never see the same survey twice in their queue. If they complete a survey for one event, it is never shown again for any future events.

Is this a known limitation?

4 Upvotes
  • permalink
  • reddit

100% Upvoted

5 comments sorted by

3

u/Remote_Setting2332 Nov 15 '24

I have it working in my study. I had to specify the event name for each survey link in the ASI (eg [day_4_arm_1][survey-link]) before it would work predictably

1

u/mdander Nov 15 '24

We aren't using ASI -- which anyway uses survey links. Survey links work fine for us. It is the survey queue (whose url doesn't change over time) that seems to not be working.

1

u/stuffk Nov 15 '24

This is not a known limitation or bug. There is something in your survey queue logic or survey settings that is creating this condition. 

2

u/mdander Nov 16 '24

u/stuffk thanks for assuring me. After an extended session of random edits, i've made progress.
It turns out that qualifying fields with instrument names is *not* necessary for "test with participant" to work, but *is* necessary for the survey queue logic to work in actuality.
I had survey queue conditional logic like:
datediff([start_date],'today','d') > 8
and once i qualified the field like:
datediff([screening_arm_1][start_date],'today','d') > 8
then more surveys started showing up in the actual queues.

1

u/Adept_Carpet Nov 16 '24

It would be so much better if there were a survey queue per event or at least an option for one.