no map/reduce or scheduled scripts processing. all stuck in pending status. only in a particular sandbox, fine in other sandbox and production account. even a simple scheduled script that just creates 1 debug log and exits, with no other map/reduce or scheduled scripts running, will not move from 'pending'. sandbox is active, there are no ongoing bulk processing events, csv imports, mass updates, scheduled scripts, map/reduce scripts, etc.

AI generated answer (using internal Slack threads):

Based on the conversations, it seems like this is a known issue that has been experienced by multiple users. Scripts, whether they are Map/Reduce or Scheduled, sometimes get stuck in 'Pending' or 'Processing' status even when there are no other scripts running. This issue seems to be more prevalent in sandbox environments. Here are a few things that were mentioned in the conversations that might help: 1. Wait it out: In some cases, the scripts eventually move from 'Pending' to 'Completed' status after a significant amount of time (up to 2 hours in some cases). 2. Create a new script record: One user mentioned that they were able to work around the issue by creating a new script record from the same script and deploying it again. However, this might not always work as the new deployment could also end up in 'Pending' status. 3. Check the performance monitor: The performance monitor might show the SuiteCloud processors as 'available' instead of 'in use', even when scripts are stuck in 'Processing' status. 4. Check for known defects: One user mentioned that they filed a case and found out that there is a known defect (Defect 630181) related to delays between stages and slow performance in SuiteScript 2.0 Map Reduce Scripts. Remember, these are just suggestions based on the conversations and might not always work. It's always a good idea to keep an eye on the status of your scripts and try different things if they get stuck. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******