You can clear the caches using the Pega API api

Cache Management (Pega API)

• REST APIs to manage VTable Cache across all nodes in the cluster
• REST APIs to manage Conclusion Cache across all nodes in the cluster
• REST APIs to manage Declarative Page Cache across all nodes in the cluster
• REST APIs to manage Declarative Rule Cache across all nodes in the cluster
• REST APIs to manage Rule Cache across all nodes in the cluster
• REST APIs to clear ABA Cache across all nodes in the cluster
• REST APIs to list and clear requestor pools across all nodes in the cluster

to use the Pega API - you can switch to the Admin Studio workspace - see https://community.pega.com/sites/default/files/help_v81/pxadminstudio/procomhelpmain.htm 

and open the Pega API page - it will list all the entry point for the Pega API 

for more details https://community.pega.com/knowledgebase/articles/pega-api-pega-platform 

Thanks Richard.  Do you know if there are any future plans to add calls to these API into the admin portal in a more user friendly type of manor?  I suppose that I could build that functionality into our environment, but I'll not worry about it if it is something that may be an enhancement in the future.

Also, just before seeing your comment, I ran the following query and did a cycle, which ultimately fixed my issue as well.  Next time, I will give the API a try.

truncate table pegadata.pr_sys_queue_ftsindexer;
truncate table pegadata.pr_sys_queues;
truncate table pegadata.pr_log;
truncate table pegadata.pc_history_work;
truncate table pegadata.pr_sys_statusnodes;
truncate table pegarules.PR_SYS_CACHE_ENTRY;
truncate table pegarules.PR_SYS_CACHE_IMPL;
truncate table pegarules.PR_SYS_CACHE_DEP;
truncate table pegarules.PR4_rule_sysgen;
truncate table pegarules.pr_assembledclasses;