Speed Texting Troubleshooting
Search
Speed Texting Troubleshooting
If a track isn't sending out text messages:
- Ensure the service is installed and FireDaemon service is running and set to automatic.
- Open the config file <C:\clubspeedapps\speed-text\config.js
- Ensure the track URL is accurate
- Ensure the Private key is correct (From the api config files)
- Go to the /admin/speedtext/settings -
- Ensure it is turned on (both 'Enable Feature for Track' & 'Enable Auto Sending')
- Make sure Provider is set to Twilio and the API User and Key is filled in (customer account) w/ at least 1 number
- Make sure they are not having issues outside their 'Cutoff Hour'
- Go to the Text Logs to see what they system is saying. You should see the following message every few seconds if it is looking for races properly:
- [INFO] Getting upcoming heats from: http://<DOMAIN>.clubspeedtiming.com/api/index.php/races/upcoming.json?key=cs-dev
- //Put the URL from the message in a new tab to see what it is pulling. If they have races scheduled but you see the following, then the API call isn't seeing the races properly.
///One way to test is to add your cell number to a test user, assign some points, and put them in the racer queue for all scheduled races. Then you can adjust the prior races and do other items and no matter when a race starts, you should be picked up.
- Make sure to approval from the track ahead of time and ask them not to remove you from the race til that is the current race they are about to start.
The way SpeedText works:
The trigger for the system to check for numbers is when a race runs. So, if they have Prior Races set to 3; they have been slow and a race starts; and they are racers in the queue 2 races out expecting a text, Those racers will NOT get a text.