I have a multi-step Zap that invokes a Sub-Zap at one step. While editing and testing the Zap, I choose the test data and then I am stepping into each step and testing it (or hitting Continue). When I hit the Sub-Zap step and run “Test step” in order to send the values and get the response, it uses whatever data was lastused to test the Sub-Zap rather than the data I chose as test data for the Zap trigger step. This isn’t what I want, of course.
I found that if I then edit the Sub-Zap and on the first step I choose “Find new records” for testing, I will then see the data from the “test” I ran in the calling Zap’s Sub-Zap step. Then when I return to the calling Zap edit window and re-run the test on the Sub-Zap step, it uses the Zap’s test data as expected.
I consider this a kludgy workaround, as I don't actually need to edit the Sub-Zap, but must do so in order to edit and test the calling Zap, leaving behind a draft edit that I don’t really care about.
Is this something I could submit as a feature request? Anyone else have any insight?
These cover testing a Sub-Zap, which can be a bit clunky.
You can submit feature requests via a ticket to Zapier Support to be logged for consideration: https://zapier.com/app/get-help
Appreciate it, Troy.
In my case I’m not actually testing the Sub-Zap, but the Zap that calls the Sub-Zap.
I think I may end up just creating a feature request.
@Special Needs Respite
FYI: Just because you submit a feature request, does not mean Zapier will ever act upon that feature request.
If you want to test the Sub-Zap you either have to test ever step of the Sub-Zap or you have to run the Sub-Zap live.
Yeah - I understand about feature requests. I didn’t see a dedicated “feature request” section, so I just opened a ticket to see what happens.
I’ve tested all my Sub-Zaps already and they work fine - just trying to edit and test a Zap that contains a Sub-Zap step - that’s where there seems to be a disconnect.
For example, in this Zap flow, there’s a call to a Sub-Zap to determine the various scenarios that an invoice might encounter (e.g. account not active, insufficient funds, etc.). Sub-Zap has been tested and works fine. However, if I’m editing for debugging or updating this Zap flow, when I hit step 8 (the call to the Sub-Zap), and choose “Retest step,” the test will run with old Sub-Zap data being returned, apparently not using the fresh test data supplied in the arguments.
That is the crux of my post.
To work around this, I found that if I open the Sub-Zap from step 8 and edit it, create dummy data, then delete the draft, I can go back to the Zap that called it, and THIS time if I run it, it is invoked as expected.
Hi @Special Needs Respite,
Thanks for highlighting the caching issue affecting your Zap's "Retest step," where old Sub-Zap data is used instead of fresh test data. Your detailed explanation and workaround are beneficial for others facing similar problems. To troubleshoot further, try clearing your browser cache or switching browsers. Since you've contacted support, they'll investigate and escalate as needed. Although there's no public feature request section, submitting a ticket to Zapier support is the right move. Your shared experience adds value to the community, and we appreciate your patience and proactive approach.
