 |
 |
 |
 |
 |
 |
 |
 |
|
|||||||||||
|
|
|
|
|
|
|
|
|
#9
11-03-2018, 11:00 AM
|
|||
|
|||
|
I just followed your instruction and forced a scheduled copy then canceled.
The notification fired and SD! is now registered. I'm running 10.14.1 but, to be clear, it SD! never registered under 10.13.x either. On the iMac I understand that is likely because I had Growl installed, but on the MacBook, I'm not sure why. Does SD! fire a notification when the copy is successful or just upon fail? If the latter that could explain why SD! never registered on my MacBook--because it never had a failed backup. That said, my guess is you have SD! set to fire on both Successful and Failed Backups, correct? If this is the case, I'm at a loss for why it wouldn't have registered before? 
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Notifications Center | tdenson | General | 4 | 08-13-2012 08:39 AM |
| Suggestion: customize your Growl "Failed" notifications | Ward | General | 0 | 12-28-2009 12:41 PM |
| MailMe notifications are blank with latest version of SuperDuper! | gadgetdoctor | General | 4 | 10-22-2009 02:37 PM |
| Script on fail? | Diggory | General | 3 | 11-28-2008 12:51 AM |
| Growl Notifications not sticking. | raptor256 | General | 4 | 12-07-2006 09:14 PM |
Threaded Mode