// live session 04
Flows that don't
break in bulkstarting in
04:12
@namastesalesforce/in/imswarnil
NSDS
01
Starting soonCountdown + title + handles. Runs 5–10 min before the hour so late joiners land on something branded, not a black frame. No live badge yet.
// live session 04
LIVE
CAMERA · full bleed
Swarnil SinghaiSalesforce Architect · host
namastesalesforce.com
NSDS
02
Full cameraThe open, the recap, and every moment you are arguing rather than demonstrating. Lower third shows for the first 8s only, then retires.
// live session 04
LIVE
SHARED SCREEN · 16:9 region
namastesalesforce.com
NSDS
03
Screen + camThe workhorse. Screen fills the stage; camera parks bottom-right at 17–20% width. Cam never overlaps the org's left nav or the record you're editing.
// live session 04
LIVE
03 · Bulkificationstep 2 of 5
SLIDE · 16:9
namastesalesforce.com
NSDS
04
Slides + camDeck teaching. The topic bar carries the mono step index — the same 01/02/03 numbering the lessons and thumbnails use, so the viewer always knows where they are.
// live session 04
LIVE
CODE · full stage, cam off
NSDS
05
Code focusCam and lower third off, safe area widened to 87%. For the two minutes where a stack trace matters more than a face. Say “I'm going full screen” before you switch.
// live session 04
LIVE
Priya Nairguest · Flow architect
NSDS
06
Guest / interviewTwo equal 16:9 cams, never one big and one small — the layout states that both people are peers. Guest's lower third appears on their first answer, not on join.
// live session 04
LIVE
// QUESTION · @dev_arun

Does a Flow element count against SOQL limits the same way an Apex query does?

namastesalesforce.com
NSDS
07
Q&AOne question on screen at a time, attributed by handle. The card is the same shape as the lesson callout — a question is content, not chat noise.
// live session 04
Next: Governor
limits, livethursday · 19:00 IST
watch the course
@namastesalesforce@namastesalesforce
NSDS
08
EndingIdentical geometry to the YouTube end screen, so the VOD's last frame and the stream's last frame are the same asset. One CTA, next session dated, handles.