# Trigger Simulation Dead?

**URL:** <https://forum.hamalert.org/t/trigger-simulation-dead/458>\
**Category:** Support\
**Created:** [December 15, 2023, 3:39pm UTC](https://forum.hamalert.org/t/trigger-simulation-dead/458 "2023-12-15T15:39:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![HB9DQM](https://forum.hamalert.org/user_avatar/forum.hamalert.org/hb9dqm/32/5_2.png) [@HB9DQM](https://forum.hamalert.org/u/HB9DQM)\
**Post date:** [December 17, 2023, 3:00pm UTC](https://forum.hamalert.org/t/trigger-simulation-dead/458/4 "2023-12-17T15:00:40Z")

</div>

I think I found the reason why this didn’t work for you. The DXCC numbers in your triggers were stored as strings rather than integers in the backend database. The web interface does not care about that, but the matching engine does. I assume it’s related to this:

> [@JSON download/upload of triggers](https://forum.hamalert.org/t/json-download-upload-of-triggers/16/3):
>
> I have created a script in PowerShell to create triggers for all missing DXCCs per band. Maybe this is useful for others so I make it available here: How to use it: Put all provided files to a folder, e.g. “c:\temp\hamalert”. Export an ADIF file to this location. Login at [hamalert.org](http://hamalert.org) and open the developer tools from your browser. Locate the PHP Session cookie for [hamalert.org](http://hamalert.org) and copy the value into your clipboard. Open the powershell script with an editor and fill in all needed informa…

I fixed your triggers in the DB, so it should work now.

---

_[View the full topic](https://forum.hamalert.org/t/trigger-simulation-dead/458)._