Frequently Asked Questions
Simian users who use the same program logs over and over, modifying it regularly to update content can run in to issues where time events do not fire correctly at there scheduled times, items get skipped over, or even repeat. The program log is a type of database and as items are moved, added, and deleted, a reference number field assigned to each event in the program log gets out of order. After a certain amount of time, typically after several weeks of constant updating, the recycled log's reference numbers get so out of whack it causes the issues described above.
To reset the reference numbers, the recycled log can be copied and pasted in to a new program log. The new program log can then be saved to overwrite the recycled log. Repeating this process on a weekly or bi-weekly schedule should avoid those types of issues going forward.
Step one: Open the program log in Production mode (in the example we are using the WED.bsi program log)
Step two: Go to Edit > Select ALL to highlight all the events in the program log
Step three: Go to Edit > Copy to copy all the highlighted items in the program log
Step four: Go to File > New Program Log to get a new, blank program log
Step five: Go to Edit > Paste to paste the previously copied events in to the new program log
Step six: Go to Log > Clear all status information to clear previously stored played status and played time data
Step seven: Go to File > Save Log As to save the program log
Step eight: Here you can choose to save the program log with the same name or give it a different name (in the example we are using the same WED.bsi file name)
Step nine: If using the same file name as previously, choose Yes to overwrite the old, recycled program log with the new reference numbers
The following image shows a comparison of the reference numbers in a recycled log that has been copied and pasted in to a new log: