Hello @Ramaswami ,
For this use case, Instead of directly hardcoding the date in query activity you can use a javascript activity in the start to initialize the variables.
Like This:
![manojk62306941_0-1591354658152.png manojk62306941_0-1591354658152.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/24546i80BE70CBB448788C/image-size/medium/is-moderation-mode/true?v=v2&px=400)
Then you can call these variables in the query activity like this:
![manojk62306941_1-1591354694691.png manojk62306941_1-1591354694691.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/24547i74C30ACE1D25318B/image-size/medium/is-moderation-mode/true?v=v2&px=400)
and then finally call the same variable in the second javascript activity to get the values like this:
![manojk62306941_2-1591354760924.png manojk62306941_2-1591354760924.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/24548i0AF0F867775808BE/image-size/medium/is-moderation-mode/true?v=v2&px=400)
And this is how the complete workflow will look like:
![manojk62306941_3-1591354813684.png manojk62306941_3-1591354813684.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/24549i9E0EC41C70172DCD/image-size/medium/is-moderation-mode/true?v=v2&px=400)
Let me know if that helps