# SSTI_SERV_EVENT_RESET (SSTI API Event)

Event fires when SSTI main script has just restarted.

## Variables

The following table shows input values (you send them with the API call) and returned output values.

| Variable |     | Required | Description |
|----------|-----|----------|-------------|
| *link_message* parameters: |     |          |             |
|          | num |          | SSTI_SERV_EVENT_RESET |
|          | str |          | \-- not used -- |
|          | id  |          | \-- not used -- |

## Comments

This event fires when SSTI server main script has got restarted. No initialization has been read at this point (group name is not known). The configuration notecard will be read after this event.

The server initialization events order is the following:


1. *Server restarted*
2. **SSTI_SERV_EVENT_RESET**
3. *Server starts reading config, this takes 10-20 seconds*
4. *Config notecard has been read, config is known now*
5. [SSTI_SERV_EVENT_INITIALIZED](/doc/45ce557b-3520-453e-8f21-3bf6deb1596f)
6. [SSTI_SERV_EVENT_GROUP](/doc/ab39cbd9-28b1-4a88-8953-33cfa44d8205) (sent without your request)
7. [SSTI_SERV_EVENT_CLOUD](/doc/a5b831dd-134a-4960-bc3d-fcdfa06246c5) (sent without your request)
8. *SSTI server starts doing its work*

**Important:** The server can be restarted by the user or sim at any moment. Be prepared to get this event at any time (for example, customer edits the configuration notecard).

## Example

This example demonstrates the arrival of SSTI initialization events


:::warning
Code sample missing: the old wiki failed to render this code block, so it was not in the source. Restore it from the original source.

:::


:::warning
Code sample missing: the old wiki failed to render this code block, so it was not in the source. Restore it from the original source.

:::