so doing it from a browser and doing it from a python script won't result in parallel requests? or will a parallel request just be delayed until rrf can respond?

is polling rr_status from a python script safe? The documentation mentions this:

Since RepRapFirmware can only process one HTTP request at a time (excluding rr_fileinfo and rr_upload on certain platforms), DuetWebControl should attempt to avoid parallel requests

but it seems like i'm connecting not to the reprapfirmware but to the duet web control which must pass through the call and return the results?

I added an S1 to one of the G1 commands because otherwise it would ignore the endstop and keep running in.. this is a corexy setup, fyi

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Sat Mar 18 2017 08:59:01 GMT-0600 (MDT)

; Relative positioning
G91

; Lift Z
G1 Z5 F6000

; Course home Y
G1 Y-305 S1
; Course home X
G1 X-355 S1

: Move away from the endstops
G1 X15 Y15 F6000

; Fine home X
G1 X-355 F360 S1
; Fine home Y
G1 Y-305 F360 S1

; Move Z down until the switch triggers
G1 Z-305 F1800 S1

; Absolute positioning
G90

; Tell the firmware where we are
G92 Z2.5

; Uncomment the following line to lift the nozzle after probing
;G1 Z5 F100

you are quick to respond!

this is my bed.g
M561

; Home all axes
G28

; Probe the bed at 4 points
G30 P0 X15 Y15 H0 Z-99999
G30 P1 X15 Y285 H0 Z-99999
G30 P2 X335 Y285 H0 Z-99999
G30 P3 X335 Y15 H0 Z-99999 S

G1 X0 Y0

I'm very new to duet or RRF and am just now trying my first prints on my cbot. I replaced a smoothieboard that i never particularly cared for. I'm amazed at how smooth/quiet it is.. i didn't know sound levels like this were possible!
I heat my bed / nozzle up before running g32. After running g32 both heaters turn off… i didn't think much of that until i put it in the startup of my print gcode. Now as soon as the g32 finishes duet thinks the print is done.

Is that normal? I've read a bunch of threads where people do something similar so I'm thinking I'm doing something wrong or maybe it has changed recently?

this is from my config.g

M558 P4 X0 Y0 Z1 H5 F120 T6000 I1 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
G31 P500 X-30 Y0 Z1 ; Set Z probe trigger value, offset and trigger height