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
8 months agoShaquana
8 months agoJuliann
7 months agoEden
7 months agoShaun
7 months agoKarrie
7 months agoRosalia
8 months agoFrederica
8 months agoMyong
9 months agoBrittney
7 months agoMa
8 months agoNickolas
8 months agoCraig
9 months agoSelma
9 months agoKenneth
8 months agoCristy
8 months agoNidia
8 months agoMiriam
8 months ago