> For the complete documentation index, see [llms.txt](https://cqube.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cqube.sunbird.org/cqube-v-4.1-beta/troubleshooting-issues/data-emission-issues.md).

# Data Emission Issues

|                                                                                        | **Where**             |                                                      | **Why**                                                                         | **How to resolve**                                                                                             |                                                                           |                                     |                                                                          |                                                 |
| -------------------------------------------------------------------------------------- | --------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------- |
| **Error message**                                                                      | **Error Location**    | **Error type**                                       | **Error identification (Cause)**                                                | **Probable resolution**                                                                                        |                                                                           |                                     |                                                                          |                                                 |
| Error: 400, f'Bad request, filename not provided in payload'                           | console emission logs | When the key/filename is not provided in the request | When the key/filename is not provided in the request                            | Provide the valid key/filename in the request body                                                             |                                                                           |                                     |                                                                          |                                                 |
| Error: 404, f'Bad request, unable to find the file - validate the filename in payload' | console emission logs | When the key/filename specified doesn't exist        | When the key/filename is provided in the request, doesn't exist in cQube bucket | Provide the valid key/filename in the request body while uploading or dowloading                               |                                                                           |                                     |                                                                          |                                                 |
| Error: 400, f'Bad request, not cqube bucket - validate the bucket name'                | console emission logs | When the bucket name specified doesn't exist         | When the bucket name provided in the request, doesn't exist                     | <p>Provide the valid bucket name in the request body while uploading or dowloading                    <br></p> | Error: 400, f'Bad request, validate the payload'    console emission logs | When the payload has missing fields | When any of the fields are missing in the payload, this issue will occur | Request with the required fields in the request |
| Error: No credentials found for given 'iss'                                            | console emission logs | When the token is not issued by cQube                | When the token is not issued by cQube                                           | The valid token issued by admin needs to be used                                                               |                                                                           |                                     |                                                                          |                                                 |
| Error: "Bad token; invalid JSON"                                                       | console emission logs | When the token is not valid                          | When the token is not issued by cQube and is invalid                            | The valid token issued by admin needs to be used                                                               |                                                                           |                                     |                                                                          |                                                 |


---

# 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://cqube.sunbird.org/cqube-v-4.1-beta/troubleshooting-issues/data-emission-issues.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.