Hi there,
I’m encountering a frustrating problem with my automation setup. Since early June, I’ve noticed that the subtasks generated through Zapier are completely empty, lacking any information.
The support team at Zapier mentioned that they believe this issue is on your side. I’m quite worried since this bug has persisted for over two weeks now. Businesses rely heavily on seamless automation to function smoothly. Could you please assist me in resolving this matter? Any updates would be greatly appreciated.
zapier’s been acting weird lately ngl. check if your api connections are still authenticated - mine expired random last month and everything looked normal but outputs were blank. also try duplicating the zap and rebuilding from scrath, sometimes thats faster than debugging the brokn one.
Had the same issue about a month ago with my Zapier setup. Turned out to be field mapping that broke after a platform update. Fixed it by going into Zapier and remapping everything in the subtask creation step - even fields that looked fine. Had to test each field one by one to make sure data was actually flowing through. Seems like some field references went stale after the update, so you’d get empty outputs even with green checkmarks showing. I’d also double-check your trigger step to make sure it’s still pulling the right data format.
I’ve hit this exact issue before. It’s usually a webhook payload problem - the source app changed how it structures its data output. Zapier gets the trigger but the data fields are null or formatted wrong now. First, check your webhook test data. Run a test trigger and look at the raw payload to see if your expected data is actually there. If the payload looks good, recreate just the subtask action step with fresh field mappings from a new test trigger. Don’t use old test data - the field structure might’ve changed quietly on the source platform.