Allowing others to pilot your experiment
People often want help with runtime errors on the forum, but either post a pilot link or a link to their project page. In the former case the pilot link has often expired before it gets used and in the latter the project page is not visible to other users unless the project is set to public. While you could set the project to public, this would mean that the person trying to help you would need to make a fork and run their own copy. They would also have access to your data (if there is any).
If your experiment isn’t running properly then you can safely set it to “running”, add some credits (if you don’t have a licence) and share the run link. Turn off “save incomplete results”. If you want to make sure that the experiment isn’t finished, add a routine at the end (or at any point after the place your want help with) with a text component and no ending condition. This is also suitable for piloting a working experiment apart from for checking the correct data is being saved.
If the error doesn’t occur near the start, either add a copy of the routine that is failing to the beginning of the flow or disable some of the intervening routines. This is especially important if you have embedded surveys with required responses. If you can’t do this, then try to replicate the error in a smaller version of your experiment.
The bottom line is – make it as easy as possible for other forum users to recreate your error, especially if you haven’t managed to identify which line of code is causing it via the developer tools.