> For the complete documentation index, see [llms.txt](https://docs.loyaltysurf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loyaltysurf.io/integrations/zapier/troubleshooting.md).

# Troubleshooting

If you are experiencing issues with your Zapier setup, you can use Zapier's Task History feature to help.

## Zapier Task History

Zapier provides a Task History feature that will allow you to view the data in/out of your Zap, as well as troubleshoot any/all issues. [Learn how you can use Task History here](https://zapier.com/learn/getting-started-guide/task-history/).

Please note that it has been observed that Zapier task history may be delayed up to 20-30 minutes. Keep this in mind when troubleshooting Zap setup.

If you contact LoyaltySurf customer support regarding Zapier issues, you will need to provide us with screenshot(s) and data payloads from the Task History so we can further investigate.

![Zap Task History](https://3285719719-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LeklWo0yn03AhWro2Ux%2F-LrnoszDOfCoAxqwVdW6%2F-Lrnp8is90KMgk5Hvf8R%2Fimage.png?alt=media\&token=b9eef3b2-8697-4131-9373-88487ed08f70)

### Sample Data

When setting up your Zap Trigger, at the "Find Data" step, you may see sample data that does not accurately reflect your campaign data. Sample data is only used to set up 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.loyaltysurf.io/integrations/zapier/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.