If it doesn't delete or rename those files (as used in our SafeCopy process) that generally means that the profile stopped, was disconnected and could not reconnect, or some other error that prevented it from doing so (or, we instructed it to be deleted, the device, etc, said it had, but it lied...).
As we don't know what your Destination is or how you are connecting to it, it's hard to speculate further.
Those files are ignored by default during 'normal' processing ('outside of' the SafeCopy function) by virtue of an exclusion filter. Whether removing that would then mean the files were deleted would depend on your settings (they could be copied to the other side instead...). A Mirror Right would likely delete them, a Backup wouldn't (and so on)
If you're using a Backup (and don't want to delete 'other' orphan files on Dest), one possibility is to create a profile that only looks for *\SBSE____.* (as an inclusion filter, with all exclusion filters removed) and is set to Mirror. Then run it periodically or routinely (perhaps as the next profile in a Group?)
Of course, it might be better to figure out why it's happening at all, and see if it can be stopped, but I guess that would need you to sign up for ticketed support, submit Support Zip with debug-out, etc. Bear in mind we can't necessarily fix errant devices/devices.
As we don't know what your Destination is or how you are connecting to it, it's hard to speculate further.
Those files are ignored by default during 'normal' processing ('outside of' the SafeCopy function) by virtue of an exclusion filter. Whether removing that would then mean the files were deleted would depend on your settings (they could be copied to the other side instead...). A Mirror Right would likely delete them, a Backup wouldn't (and so on)
If you're using a Backup (and don't want to delete 'other' orphan files on Dest), one possibility is to create a profile that only looks for *\SBSE____.* (as an inclusion filter, with all exclusion filters removed) and is set to Mirror. Then run it periodically or routinely (perhaps as the next profile in a Group?)
Of course, it might be better to figure out why it's happening at all, and see if it can be stopped, but I guess that would need you to sign up for ticketed support, submit Support Zip with debug-out, etc. Bear in mind we can't necessarily fix errant devices/devices.