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
1 months agoShaquana
2 months agoJuliann
2 days agoEden
3 days agoShaun
8 days agoKarrie
11 days agoRosalia
2 months agoFrederica
2 months agoMyong
2 months agoBrittney
24 days agoMa
27 days agoNickolas
1 months agoCraig
2 months agoSelma
2 months agoKenneth
26 days agoCristy
29 days agoNidia
1 months agoMiriam
1 months ago