Today we were testing running ForecastBuilder for one of our backup sites. Our plan was just to test to ensure the process was working how it is intended to in the event we have a prolonged backup situation. We did not publish or anything but the auto-saving that happens between steps seems to over-write what is in the ISC database for that office. So neighbors of that office think they have changed their forecast when really we are just testing something. Seems like this is easily changed by having the office just re-save all their grids.
Not sure if there is really a way around that issue when testing, but I wanted to make people aware since many others may be testing backup capabilities in the coming days.
Anyone else have any comments or best practices as it pertains to ForecastBuilder while in backup mode?