You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking in to the code, the Orca file is saved whenever a new standard run is started if the document is edited. So, for most of the graveyard shift, the runs were rolling over and the Orca file is not expected to be saved again during these run rollovers. However, when the run was initially switched into Maintenace from a TELLIE run it should have saved. I will take a look at the log file, but nominally it seems like there may be a problem with the document claiming that it hasn't been edited and thus Orca doesn't save the file when switching standard runs.
The text was updated successfully, but these errors were encountered:
Based on reports in these two shift reports: https://snopl.us/shift/view/4734a245d839440a9c40ed1c6e6217a4 and https://snopl.us/shift/view/53f0c065d09b4028b6d1087fbf8a7dc7 it seems as though the Orca file wasn't correctly being saved.
Looking in to the code, the Orca file is saved whenever a new standard run is started if the document is edited. So, for most of the graveyard shift, the runs were rolling over and the Orca file is not expected to be saved again during these run rollovers. However, when the run was initially switched into Maintenace from a TELLIE run it should have saved. I will take a look at the log file, but nominally it seems like there may be a problem with the document claiming that it hasn't been edited and thus Orca doesn't save the file when switching standard runs.
The text was updated successfully, but these errors were encountered: