> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/faqs-and-common-issues/why-am-i-not-receiving-injects.md).

# Why am I not receiving injects?

If you're not receiving injects, we recommend checking a few things in your Editor first:&#x20;

#### Are you sending injects to specific teams or positions that are not currently assigned?

If you're logged in as a player who isn't part of the **team / position** set to receive certain injects, you won't see them in your player view / Virtual Desktop.

For most players, this is intended. But if you're a Facilitator looking to test your exercise, you can resolve this by:&#x20;

* Setting up your **teams table** in the Editor

{% content-ref url="/pages/ezFsBUecds4TROGiLo7j" %}
[Setting up your teams table](/feature-documentation/designing-and-running/teams-roles-positions-and-groups/setting-up-your-teams-table.md)
{% endcontent-ref %}

* Assigning **positions** (before and during the exercise)

{% content-ref url="/pages/1q7diU7DdvzY3hRdt3o9" %}
[How to assign Roles & Positions](/feature-documentation/designing-and-running/teams-roles-positions-and-groups/impersonation/players-personas-and-role-players/how-to-assign-roles-and-positions.md)
{% endcontent-ref %}

* Using **Grid View** to test different player views

{% content-ref url="/pages/GOen5zZL51ujLa56hgD0" %}
[Grid View](/feature-documentation/designing-and-running/facilitation/grid-view.md)
{% endcontent-ref %}

#### Are the correct **channels activated**?&#x20;

In your Editor, check under `Configuration` > `Channels` that the correct channels are activated. Your Verifier (the bell icon in the top left of your Editor) will notify you of any disparities between injects and what's activated.

You can also check that persona social media profiles are activated under `Personas`.

{% hint style="warning" %}
If none of the above are applicable, **please raise a ticket with** [**support**](#user-content-fn-1)[^1].
{% endhint %}

[^1]: <support@conducttr.com>


---

# 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://helpdocs.conducttr.com/faqs-and-common-issues/why-am-i-not-receiving-injects.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.
