Troubleshooting

Station stays offline

Check that the Python process is running with --listen, then verify its MQTT host and port, station ID, organisation ID, username, and password. Confirm the jig can reach the broker. If credentials were rotated, update the protected environment and restart the process.

Station connects but cannot fetch data

Check the station API base URL and HTF_API_KEY. A revoked key or a key for a different station cannot access that station's data. If a station secret was changed, restart or reconnect the station so it fetches the new value.

Run fails at a programming stage

Open the run's stage result and logs. Confirm the programmer is connected, its serial number and target device match the jig, and the configured firmware image and path exist. Try the equivalent hardware command on a bench only after preserving the original run evidence.

ID pool is exhausted or a value is reserved

Open DUT records & IDs to review available rows, reservations, and commits. A claimed linked row stays with its DUT after a failed run. Inspect that DUT and its assignment history, then retry with the same DUT ID after confirming whether any external service consumed the values.

Still stuck?

Keep the station ID, DUT ID, run time, first failing stage, and relevant log lines together when asking for help. Do not include passwords, API keys, or secret values. Contact Embeint if you need support.