Yesterday I got myself a Failed to schedule report error.
After some testing I found the reason: Don’t use a double quote as the first character of your Dashboard name, as this will effectively prevent you from setting up scheduled deliveries.

I myself find it a bit annoying, so I started digging into what’s actually happening to those settings when you hit the Save button.
The explanation is quite funny, only a few of the settings are actually saved in the way you would expect them to be saved, that is as properties tied to your login. Most of the settings are only stored locally on the computer you are currently using to change the settings.

The settings you can count on are :

• Include Calendar Events in Reports
• Enable network acceleration for improved report performance
• Currency
• Scheduled Report Encoding

The rest, you’ll have to adjust on every computer you use for SiteCatalyst.

Workarounds:

• Switch to Kubuntu or some other NON-Gnome based Linux distro
• Make your Ubuntu installation capable of running with the KDE desktop manager (sudo apt-get install kubuntu-desktop)

This is what the Danish characters æ ø and å looks like inside Discover: (perfect)

This is the same data after being exported in Excel format by Omniture Discover: (not pretty)

SiteCatalyst

When setting the scheduling options in a report scheduled for later delivery in SiteCatalyst You’ll see a dialog box pretty much like this, notice the lack off timezone indication next to the “Time of day” dropdown.

So what timezone is this? Is it Utah time? No, it’s in fact your local timezone, this will become obvious if you try editing an existing report, in this case you’ll see the timezone indicator next to the “Time of day” dropdown.

I know, no big deal, just confusing, especially for the new SiteCatalyst user.

Data Warehouse
Schedule editing in Data Warehouse is not that different from SiteCatalyst, but there is one big difference you need to be aware about. Even though the dialog box shows you that things will execute at a certain time in your local timezone, this isn’t what really happens, everything in Data Warehouse happens at Pacific Standard Time (I think it is).
Being located in Denmark as I am, this means that the earliest possible time at which I can get a Data Warehouse request to execute is 9 AM local Danish time if I need yesterdays data included in the report.

One of the supposedly great features of customers.omniture.com is a System status grid where you can get updates on the current system status of the Omniture production environment, needless to say that for such a System status grid to be really smart, it has to be running even when everything else isn’t.
Perhaps Omniture should make customers.omniture.com a bit more of a standalone system, without any ties to the rest of the Omniture network. I myself would probably even move the system to a location outside the Omniture network, this way customers.omniture.com could be available even in a situation where Omniture suffers from a complete network blackout.

Workaround:

• Setup your report suite to display a Dashboard as the SiteCatalyst startpage.

I’ve especially noticed a minor change made to the conversion classification editor.
Prior to the 9/17 maintenance release, deleting a child numeric classification was impossible, You got no reaction from the editor when trying. This behaviour has changed a bit, trying to delete a child numeric classification now results in the parent being deleted instead, and when you recreate the lost parent classification the child magically re-emerges as well.
I’m still trying to figure out the purpose of this change.

Update:
Here is a video demonstrating the strange conversion classification editor behaviour.

Click here to view the embedded video.