I agree with Selma. B and D are the way to go. Gotta have that dedicated queue processor to keep things running smoothly across all those different time zones.
Ha! Midnight GMT, huh? Sounds like a real nightmare for the poor dev who has to deal with that. I'd go with B and D, just to make sure those global operations don't keep the rest of us up all night.
Hmm, I'm not so sure. I was thinking A and C would work better. A standard queue processor should be able to handle this use case, and the Run in background step seems more straightforward than a dedicated queue processor.
I think B and D are the correct options. Using a dedicated queue processor with the Queue-For-Processing method and the Run in background step in the case life cycle seems like the best way to handle the global operations starting at midnight GMT.
Craig
10 months agoShaquana
10 months agoJuliann
8 months agoEden
8 months agoShaun
8 months agoKarrie
9 months agoRosalia
10 months agoFrederica
10 months agoMyong
10 months agoBrittney
9 months agoMa
9 months agoNickolas
9 months agoCraig
10 months agoSelma
10 months agoKenneth
9 months agoCristy
9 months agoNidia
9 months agoMiriam
10 months ago