Hi Brandy,

I tested this issue and it appears that the API has been changed which means the Xtension is not configured correctly.
I have attached an ”Unofficial fix” (I fixed it myself) for the issue.
The Xtension now points at the correct endpoint for workflow instances. (I may have broken some of the other actions because I don’t think the endpoint has changed for all of the methods.)
With the new API there is no Option to filter via “all” so I have made the Status not a required field.  Leaving it blank will give you all workflows. 

I will get the Gallery updated with a fully working “Official version” Xtension after the holiday break.

We apologise for the inconvenience.

My issue right now is the limitations or it only wanting to return 30 back. We are looking to return between 500-1000, if possible, so we can put a condition in the workflow to alert our team to go “monitor” why it’s above our average. This is specifically to ensure excessive “trigger” looping is not occurring in our tenant causing the initiation of instances to spike! Which happened to us a few times over the years. Unfortunately, we don’t catch them immediately to pause the workflow long enough to stop / disrupt the behavior.