FaustJs/WordPress Custom Block Caching Bug

[dburkhart07]

Context:
In our current pages, we are querying for custom blocks, and displaying that data on our frontend. We know we have set this up correctly, since our query on Apollo Sandbox is returning the proper data. However, on the frontend, it seems that any updates to the wordpress site through the block editor (eg: editing a block, or adding a new one), is not being tracked and properly registered on our new app. We can see this in that, the query that is being run in our page is not getting updated, so the new data is not geting rendered. This is believed to be a problem with how our app handles caching, to which we need to fix.

How to Reproduce:

• Launch our app, and navgiate to the leadership page
• Observe what content is there already
• Go into the WP block editor (https://www.nefac.org/wp-admin/post.php?post=22290&action=edit), login (if you do not have credentials yet, message Troy), and make any change
• Save the changes, and publish the site if need be
• Observe the difference in the query that is executed in the app, and how it is executed in Apollo

Dev Implementation Notes
Troy and I (Dalton), have ruled that the issue likely lies within GoDaddy, Sucuri, Apollo or the browser itself. The only thing we have been able to rule out is that it is not related to NextJs, since NextJs caching only applies to app routing, where we are using page routing.

Some things we have tried so far to have no success:

• Restarting the computer
• Clearing the cache within the local files/file explorer
• Adding no cache to the GraphQL query done in the index.tsx file
• Using the User Agent Switcher Chrome extension to try going onto the page, making an update, and switching the browser and clearnig the cache
• Trying to adjust changes in several different browsers (this issue is occuring on Chrome and Edge so far)

This ticket will likely require some research into the caching of the other tools we are using in this app. For any questions, message Troy or I.