> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/integrations-and-plugins/integrations/fhir-beta/troubleshoot-fhir.md).
# Troubleshoot FHIR
Find solutions to common issues when working with FHIR data in Kizen Agentic Workflows.
{% hint style="success" %}
**Audience:** Admins, Developers, Solution Architects
**Purpose:** Describes troubleshooting methods for issues with the FHIR integration
{% endhint %}
The following table presents solutions to common issues with the FHIR integration. For additional help, see the [official FHIR documentation](https://hl7.org/fhir/R4/).
| Issue | Cause | What to do |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You weren't authorized to perform a FHIR action step in the space.vars.automation. | Either you didn't create an access token, or your token has expired. | Confirm that your space.vars.automation begins with the FHIR Authenticate action. Re-run the space.vars.automation. |
| You received a single page of search results from the FHIR Search action. | This is expected behavior. The FHIR Search action returns the first page of results only. | Use `_count` to control the page size of the results. Add logic to the space.vars.automation to handle pagination manually. |
| A FHIR Search action in your space.vars.automation timed out. | An extensive search can exceed the timeout limit of 30 seconds. | Streamline the search. |
| Your batch import didn't create as many space.vars.entities in space.vars.Kizen\_company\_name as you expected. | The maximum payload for a space.vars.smartconnector is 256 kilobytes. | Manually prepare multiple smaller batches, and import them into space.vars.Kizen\_company\_name sequentially. |
| You added the integration secret, but you received an error message that the secret is missing. | You added the integration secret to the integration configuration, not the Integration Secrets Manager in space.vars.Kizen\_company\_name. | Add the integration secret to the Integration Secrets Manager. See [Set Up FHIR in Kizen](/docs/integrations-and-plugins/integrations/fhir-beta/set-up-fhir-in-kizen.md) for details. |
***
## What's Next
To put these troubleshooting tips into better context, see [FHIR - Beta](/docs/integrations-and-plugins/integrations/fhir-beta.md) for a big-picture discussion about the FHIR integration.
Related Topics
* [FHIR - Beta](/docs/integrations-and-plugins/integrations/fhir-beta.md)
* [Set Up FHIR in Kizen](/docs/integrations-and-plugins/integrations/fhir-beta/set-up-fhir-in-kizen.md)
* [Authenticate to a FHIR Server in an Agentic Workflow](/docs/integrations-and-plugins/integrations/fhir-beta/authenticate-to-a-fhir-server-in-an-agentic-workflow.md)
* [Read and Write FHIR Data in an Agentic Workflow](/docs/integrations-and-plugins/integrations/fhir-beta/read-and-write-fhir-data-in-an-agentic-workflow.md)
* [Synchronize Data Between FHIR and Kizen in an Agentic Workflow](/docs/integrations-and-plugins/integrations/fhir-beta/synchronize-data-between-fhir-and-kizen-in-an-agentic-workflow.md)
***
*HL7, FHIR, and the FHIR FLAME DESIGN are the registered trademarks of Health Level Seven International, and their use does not constitute endorsement by HL7.*
---
# 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://developer.kizen.com/docs/integrations-and-plugins/integrations/fhir-beta/troubleshoot-fhir.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.