> For the complete documentation index, see [llms.txt](https://cranford-tech.gitbook.io/freelancer-marketplace/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cranford-tech.gitbook.io/freelancer-marketplace/key-payment-features/debugging-errors.md).

# Debugging errors

If you have not correctly set up either the Stripe Connect - Marketplace plugin or your actual Stripe account, you may get the following error message when running workflow actions:

*Plugin action Stripe Connect - {workflow action name} error when parsing the response: the key error is not part of the btype definition*

There is usually a straightforward fix for this. The best way to troubleshoot the error is to:

1. Go to the Developers section of your Stripe dashboard
2. Examine the logs
3. Go to the 'Failed' section and click on the most recent error
4. You should be able to see an error message that explains what was causing the issue

<figure><img src="https://cranford-tech.gitbook.io/~gitbook/image?url=https%3A%2F%2F445589018-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FOYowMYV4NApuJz7Z6lKJ%252Fuploads%252FoMQmUIw22K2LQoDmXBQc%252Fimage.png%3Falt%3Dmedia%26token%3Dcff50139-2ab1-4bd6-8388-d04fc99ce3e2&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=8ef55a6e&#x26;sv=1" alt=""><figcaption></figcaption></figure>

If you have followed these steps and still can't figure out the issue, you can contact the Cranford Tech Team and request [support](https://cranford-tech.gitbook.io/stripe-connect-marketplace/useful-tips/support).

[<br>](https://cranford-tech.gitbook.io/stripe-connect-marketplace/common-payment-flows/charge-a-customer-using-saved-payment-details)


---

# 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://cranford-tech.gitbook.io/freelancer-marketplace/key-payment-features/debugging-errors.md?ask=<question>&goal=<endgoal>
```

`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.