Troubleshooting GatsbyJS and GraphQL Sorting and Deployment in WordPress

I have a client who needs someone to troubleshoot and resolve an issue with GatsbyJs and plugins “gatsby-source-graphql” and “gatsby-source-wordpress”. The ideal candidate will need to be an expert in GraphQL queries and GatsbyJs deployment to sort WordPress posts by updated date, instead of by publish date in the GraphQL query. It would be nice if you also have experience deploying a GatsbyJs site for WordPress blog with over 3,000 posts. The client is currently experiencing issues with deployment methods that separates builds in two batches that are divided by a cut-off date in the GraphQL queries. The first batch builds posts published prior to the cut-off date and the second batch builds posts published after the cut-off date. They would like to change this so that the GraphQL queries use “updated” date instead of “published” date. Their previous efforts were not successful and they need help to resolve this. Furthermore, they would appreciate some basic training for their team to keep them from hitting this problem again in the future. Snippet of GraphQL query used: query GET_POSTS($cutoffMonth:Int $cutoffYear:Int $retiredCategories:[ID] $first:Int $after:String){ wordpress { allSettings { generalSettingsUrl } posts( first: $first after: $after where: { categoryNotIn: $retiredCategories, orderby: {field: DATE, order: DESC}, dateQuery: {after: {year: $cutoffYear, month: $cutoffMonth}} } ) { pageInfo { endCursor hasNextPage } nodes { id databaseId title link date excerpt categories { nodes { name, databaseId } } } } } }