Failed 1CP should be a Big Deal in Service Studio

By Justin James on 9 Jan 2014
A lot of times I'll do a 1CP on one eSpace, then go work on another eSpace... only to discover 30 minutes later that my 1CP failed (usually due to concurrent publications), which means that when I re-try I have a big merge. A failed 1CP should bring up an immediate, modal alert in Service Studio so the developer knows that a publish failed and can take immediate action.

Kilian Hekhuis27 Feb 2014
Only optional! And while we're at it, SS shouldn't show 1CP as failed when it fails to connect to the debugger (which is about always, directly after publishing due to time-outs).