> For the complete documentation index, see [llms.txt](https://docs.growsurf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.growsurf.com/integrations/zapier/troubleshooting.md).
# Troubleshooting
## Zap History
Zap History helps you keep track of everything that Zapier has tried to automate for you. It logs all the activity in your Zaps and transfers, including the data moved from one step to another. This is useful when trying to figure out what went wrong, and a fix is needed. To learn more, visit [View and manage your Zap history](https://help.zapier.com/hc/en-us/articles/8496291148685-View-and-manage-your-Zap-history).
When attempting to address issues with your Zap, it's important to remember that Zapier will perform a check for new data on your Zap every 1 to 15 minutes, based on your Zapier plan.
If you contact GrowSurf support regarding Zapier issues, you will need to provide us with screenshot(s) and data payloads from the Zap History so we can further investigate.
### Test Data
The data used for testing may not accurately represent your campaign data, as it is solely intended for configuring the Zap. When the Zap triggers for a live campaign, real data will be provided in the Zap.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.growsurf.com/integrations/zapier/troubleshooting.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.