http://discuss.findingfive.com/ Mon, 20 Apr 2026 06:57:26 +0000 MyBB http://discuss.findingfive.com/showthread.php?tid=242 Thu, 01 Dec 2022 13:48:15 +0000 Ting]]> http://discuss.findingfive.com/showthread.php?tid=242
We have discovered an issue with how stimulus files were handled in the latest study grammar version. If you had launched a session in the past week that required external stimulus files, it might have reported network errors to participants. This issue is now fixed, thanks to the timely report by Yilmaz Dogukan Ozlu from University of Arizona.

We highly recommend stopping the current session and launching a new one. You only need to do so if:

• Your session is launched under the latest Study Grammar version (i.e., you previewed your experiment within the last 2 weeks)
  
• Your experiment uses stimulus files.
  

You are not affected if you haven't launched a new session within the past two weeks.

We apologize for the inconvenience caused by this technical issue. Thank you so much for your patience, and we'll strive to further improve our infrastructure to minimize the chances of such incidents in the future.

Sincerely,
FindingFive]]>
We have discovered an issue with how stimulus files were handled in the latest study grammar version. If you had launched a session in the past week that required external stimulus files, it might have reported network errors to participants. This issue is now fixed, thanks to the timely report by Yilmaz Dogukan Ozlu from University of Arizona.

We highly recommend stopping the current session and launching a new one. You only need to do so if:

• Your session is launched under the latest Study Grammar version (i.e., you previewed your experiment within the last 2 weeks)
  
• Your experiment uses stimulus files.
  

You are not affected if you haven't launched a new session within the past two weeks.

We apologize for the inconvenience caused by this technical issue. Thank you so much for your patience, and we'll strive to further improve our infrastructure to minimize the chances of such incidents in the future.

Sincerely,
FindingFive]]> http://discuss.findingfive.com/showthread.php?tid=224 Wed, 25 May 2022 15:30:06 +0000 Ting]]> http://discuss.findingfive.com/showthread.php?tid=224 http://discuss.findingfive.com/showthread.php?tid=129 Tue, 27 Jul 2021 14:01:28 +0000 Ting]]> http://discuss.findingfive.com/showthread.php?tid=129
Thanks to a timely report from the LEAP lab at University of Arizona, we have discovered a new bug in the latest version of Google Chrome (v.92) that has impacted some of FindingFive's functionalities. Studies featuring many audio and video stimuli, including audio recordings that result from the audio responses, may become stuck at certain point, with an error message from FindingFive warning about missing stimulus file or incorrect format. Since this is a browser-level bug, your currently active sessions may be affected as well.

The cause
This is a new bug introduced by Google. Google is already working on a fix (https://bugs.chromium.org/p/chromium/iss...144736#c27).

Actions on FindingFive's end
We are also working to identify a workaround. However, since this is a browser-level bug, a fix might not be trivial. We will update everyone as soon as we have more insights into this issue.

What you can do
If your study features many audio and video stimuli, or use audio recording responses, please preview them immediately to see if you are impacted. If so, you can ask participants to use Firefox instead of Google Chrome to complete your study until either Google or FindingFive implements a fix.

Thanks for your patience and understanding!]]>
Thanks to a timely report from the LEAP lab at University of Arizona, we have discovered a new bug in the latest version of Google Chrome (v.92) that has impacted some of FindingFive's functionalities. Studies featuring many audio and video stimuli, including audio recordings that result from the audio responses, may become stuck at certain point, with an error message from FindingFive warning about missing stimulus file or incorrect format. Since this is a browser-level bug, your currently active sessions may be affected as well.

The cause
This is a new bug introduced by Google. Google is already working on a fix (https://bugs.chromium.org/p/chromium/iss...144736#c27).

Actions on FindingFive's end
We are also working to identify a workaround. However, since this is a browser-level bug, a fix might not be trivial. We will update everyone as soon as we have more insights into this issue.

What you can do
If your study features many audio and video stimuli, or use audio recording responses, please preview them immediately to see if you are impacted. If so, you can ask participants to use Firefox instead of Google Chrome to complete your study until either Google or FindingFive implements a fix.

Thanks for your patience and understanding!]]> http://discuss.findingfive.com/showthread.php?tid=97 Wed, 21 Apr 2021 01:51:47 +0000 Ting]]> http://discuss.findingfive.com/showthread.php?tid=97
We have identified the cause and the fix will be applied tomorrow, April 21, 2021. Previewing your study may be required in order to launch a new session after this fix is live.]]>
We have identified the cause and the fix will be applied tomorrow, April 21, 2021. Previewing your study may be required in order to launch a new session after this fix is live.]]> http://discuss.findingfive.com/showthread.php?tid=95 Thu, 15 Apr 2021 18:59:25 +0000 Ting]]> http://discuss.findingfive.com/showthread.php?tid=95
We have just been informed by our upstream provider of a database outage that has unfortunately led to partial loss of uploaded stimulus files. While the occurrence of such incidents is completely out of our control, we are assessing and implementing new measures for avoiding similar issues in the future. At this point, our analysis indicates that this will only affect you if you:

• Have collaborators who use identically named stimulus files across different FindingFive accounts.
  
• Use the US server (the EU server is not affected)
  

We were able to use our backup data to restore most of the stimulus files. As a result, we estimate about 1-3% of stimulus files may need re-uploading. Most of the affected studies were created before August 2020.

No participant data loss
We are 100% confident that there are no loss of participant data.

Active sessions may be affected, but relaunching a new session is not necessary
If your active sessions use stimulus files that are affected, participants won't be able to successfully complete them at this moment. You must re-upload those files right now. Once they are uploaded, there's no need to relaunch the session. The active sessions will automatically work again.

We apologize for the hassle. Thank you for understanding and supporting FindingFive.]]>
We have just been informed by our upstream provider of a database outage that has unfortunately led to partial loss of uploaded stimulus files. While the occurrence of such incidents is completely out of our control, we are assessing and implementing new measures for avoiding similar issues in the future. At this point, our analysis indicates that this will only affect you if you:

• Have collaborators who use identically named stimulus files across different FindingFive accounts.
  
• Use the US server (the EU server is not affected)
  

We were able to use our backup data to restore most of the stimulus files. As a result, we estimate about 1-3% of stimulus files may need re-uploading. Most of the affected studies were created before August 2020.

No participant data loss
We are 100% confident that there are no loss of participant data.

Active sessions may be affected, but relaunching a new session is not necessary
If your active sessions use stimulus files that are affected, participants won't be able to successfully complete them at this moment. You must re-upload those files right now. Once they are uploaded, there's no need to relaunch the session. The active sessions will automatically work again.

We apologize for the hassle. Thank you for understanding and supporting FindingFive.]]> http://discuss.findingfive.com/showthread.php?tid=74 Sun, 14 Mar 2021 13:39:55 +0000 Ting]]> http://discuss.findingfive.com/showthread.php?tid=74
Affected users
We are not aware of any production study being affected by this bug.

Remedies
A fix has been identified and is currently being tested. We expect to release this fix in the week of 03/14/2021.]]>
Affected users
We are not aware of any production study being affected by this bug.

Remedies
A fix has been identified and is currently being tested. We expect to release this fix in the week of 03/14/2021.]]> http://discuss.findingfive.com/showthread.php?tid=72 Sun, 14 Mar 2021 02:17:38 +0000 Ting]]> http://discuss.findingfive.com/showthread.php?tid=72
We have discovered a bug that may have resulted in partial loss of audio recording data. This bug has been fixed. The purpose of this post is to raise awareness in case you are affected by this bug and haven't noticed it yet.

If you collected audio recording data using the "background audio response" between February 04, 2021 and March 12, 2021, the audio recordings were not saved if and only if your study meets all the following criteria:

• The background audio response was used for collecting audio recordings
  
• The background audio response was set to show the volume visualizer
  
• Your study used the "duration" parameter in trial templates that involve the background audio response
  
• Your study did not use the "duration" parameter in the background audio response
  

As long as any one of the above statements does not apply to your study, your data are safe! However, for those who are affected, we are extremely sorry that the audio recordings are permanently lost. Our sincere apologies!

Remedies
Please do not use the trial-level "duration" parameter for any response-level control. You should always look for solutions that are part of individual responses. In this instance, one should always use the "duration" parameter of an audio response (background or not) for controlling the length of an audio recording.

The most effective way to avoid and help FindingFive catch unpleasant bugs like this is to always preview your study all the way to the end and examine the preview data before launching a new session. We will fix any issues noticed in previews as soon as possible.]]>
We have discovered a bug that may have resulted in partial loss of audio recording data. This bug has been fixed. The purpose of this post is to raise awareness in case you are affected by this bug and haven't noticed it yet.

If you collected audio recording data using the "background audio response" between February 04, 2021 and March 12, 2021, the audio recordings were not saved if and only if your study meets all the following criteria:

• The background audio response was used for collecting audio recordings
  
• The background audio response was set to show the volume visualizer
  
• Your study used the "duration" parameter in trial templates that involve the background audio response
  
• Your study did not use the "duration" parameter in the background audio response
  

As long as any one of the above statements does not apply to your study, your data are safe! However, for those who are affected, we are extremely sorry that the audio recordings are permanently lost. Our sincere apologies!

Remedies
Please do not use the trial-level "duration" parameter for any response-level control. You should always look for solutions that are part of individual responses. In this instance, one should always use the "duration" parameter of an audio response (background or not) for controlling the length of an audio recording.

The most effective way to avoid and help FindingFive catch unpleasant bugs like this is to always preview your study all the way to the end and examine the preview data before launching a new session. We will fix any issues noticed in previews as soon as possible.]]>