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