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