> For the complete documentation index, see [llms.txt](https://manual.senseforce.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.senseforce.io/manual/sf-platform/event-schema-management/faq-and-troubleshooting.md).

# FAQ and Troubleshooting

## What can and can not be changed/deleted **BEFORE** publishing?

You can change and delete everything except the schema can not be deleted.

## What can and can not be changed/deleted AFTER publishing?

You **can change** the name of the schema or of the attribute. You can also change the unit of an attribute.\
You **can not change** the key of a schema or attribute. You can not also change the data type or the decimals of an attribute.

## Which data type should I use for which attribute?

* **String** for text or single characters (variable unlimited length).
* **Boolean** for true/false values.
* **Long, Integer** (64 bit/32 bit) for signed and unsigned integers.
* **Double** (64 bit) floating-point number for representation of decimals.
* **Timestamp** for UNIX timestamps in milliseconds.
* **Time** is not used anymore (deprecated).
* **None** is not used anymore (deprecated).

All columns are also allowed to have NULL entries.

## Do I need to define attributes like Thing or Timestamp as well?

No, the Thing and Timestamp columns are metadata. Every schema automatically has all metadata columns, which are: Id, Inserted, Size, Thing, Timestamp, Type.

## The messages sent include all attributes defined in the event schema but the messages are put into "invalid messages". Why?

This could have several different reasons.

1. Any value in the message is of the wrong data type
2. Any value in the message includes an unexpected symbol
3. There are some additional attributes that are not defined in the event schema


---

# 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://manual.senseforce.io/manual/sf-platform/event-schema-management/faq-and-troubleshooting.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.