This topic has nothing to do with the difference between SD Card Continuous vs Motion Event Recording.
Everything we have discussed above has been dealing with triggering Cam B to upload a Cloud Event Video when Cam A encounters a Motion Event.
In this case, when Cam A encounters a motion event, it uploads that event to your account on the cloud server. Depending on your subscription, that Cloud Event could be a snapshot (none), a 12s video (CPL), or a full length video (CP). When that Cloud Event hits the server, it triggers the Rule to Cam B which then uploads a 12s Automation Event Video to your account on the server. Everything accomplished so far is all Server side. Server Event Recordings can never be continuous.
But the Event Upload Recordings have nothing to do with the SD Card Recordings. Those are completely separate MP4 video files saved to the SD Card.
In both of these cases, the Cam A initial Event Upload and the Cam B Automation Event Upload, the Event is viewed in the Events Tab where there is a link bar button for "View Playback. In both cases, pressing that button will launch to the SD Card Playback Video from the SD Card.
On Cam A, that was triggered by the Motion Event, there will be a video of the event. That video, if SD card recording is set to Motion Events, will be 1, 2, 3 minutes long depending on how long the event lasted, but always in increments of one minute because of the way SD Card Video is recorded. If set to continuous, the timeline will be 100% solid video for the duration. But, the View Playback link will still take you to the time of the event.
On Cam B this is not the case. Cam B did not see or get Motion Activated by a motion event. It was triggered to upload from a rule. So, if you have Cam B set to record to the SD Card for Motion Events only, there will be no video on the SD Card because it saw no motion. There will only be SD Card Video footage if Cam B is Motion Activated itself. If you have it set to record to the SD Card Continuously, there will be video available when you press the View Playback button from the Automation Event Upload regardless of if it experienced a Motion Activation or not.
Also consider that while Cam B is uploading the 12s Automation Event Upload triggered by the Rule, it cannot also upload a Motion Event if it does encounter Motion Activation within that 12s. The cam cannot upload two videos simultaneously which go to different areas on the server.
The SD Card is constantly recording when “Record to SD Card” is enabled regardless of whether it is set to Continuous or Motion Events. It records every minute in an MP4 file from second 00 to second 59. If set to Continuous, it saves every one minute MP4. If set to Motion Events, it only saves the one minute MP4 files that have motion activation, or multiple motion activations. It deletes those without motion activations immediately. If a motion activation occurs at second 55 in the minute and continues to second 05 in the next minute, there will be two MP4 files and the Motion Event on the SD Card will be two minutes long starting at second 00 of the first minute and ending at second 59 of the second minute.
I’m really not sure what the benefit is to to only recording Motion Events to the SD Card except for a longer SD Card history. If either Cam is Motion Activated, it uploads. That upload is directly linked to the exact time of the Event on the SD Card Video. There is no need to search and scrub the SD Card when it launches straight to the SD Video of that time from the Event Upload regardless of if the SD is set to record in either Continuous or Motion Event.