START HERE
First prove that a local timer command changes the OBS clock. Then compare the authorized channel and event rules with a single event's JSONL record. An alert preview is not a real Twitch EventSub event, and an intentional duplicate rejection is not the same as a missed event.
Establish what works before testing Twitch
Use the paused local-clock test first. A frozen OBS display makes every event look missing. Record the timer build and the configuration folder you launched; this guide follows the linked source revision, whose event implementation matches the v1.0.0 tag checked on November 18, 2026.
Choose a recent event with a known approximate time and type. There is no need to buy repeated test subscriptions or Bits while investigating. A Streamlabs or StreamElements test alert only proves that provider can animate an overlay; it does not create a real subscription, Cheer, or redemption for this timer.
Confirm the authorized channel and restart after edits
Check TARGET_CHANNEL in config.py against the intended Twitch channel. At authorization, use the broadcaster account whose events the timer must read. A browser already signed in to a different account can make the approval flow look successful while granting the wrong access.
Restart the timer after changing configuration, and read the startup output before minimizing its terminal. Preserve user_token.json during normal updates; do not delete saved authorization as the first response to a temporary network failure. If Twitch rejects the authorization or newly requested access needs approval, complete the new authorization deliberately. Never post the token file or approval code in a support thread.
Check the event-specific rule
| Event | Configuration to inspect |
|---|---|
| Bits | TRIGGER_BITS_VALUE sets the minimum; BITS_VALUE sets seconds per Bit. |
| Subscription | Check the applicable TIER_1_VALUE, TIER_2_VALUE, or TIER_3_VALUE. |
| Channel Points | CHANNELPOINTS_ALLOWED must be enabled. Match the reward title to CHANELLPOINTS_REWARD_NAME; that spelling is the actual setting name. |
| Unexpected extra time | Check RANDOMIZER_ENABLED and the corresponding bonus ranges before assuming duplication. |
Keep the original settings before experimenting. For an understandable rehearsal, temporarily turn randomization off, then restore your chosen rules. Do not reinterpret a normal timed decline as an incorrect addition: compare while the clock is paused or account for elapsed countdown time.
Read one event record alongside the startup record
With LOG_ENABLED = True, the default event log is logs/events.jsonl beside the application. Each line is a separate JSON object. Find the startup record for the run being investigated, then the event near the recorded time. Its effective settings are more useful than a configuration file edited afterward.
Compare requested_seconds, timer_delta_seconds, and reason. Reasons such as duplicate_event or duplicate_subscription explain a zero addition; a tier_upgrade can credit a difference rather than a full second subscription. Gift bundles can produce both recipient events and a separate bundle-bonus record. Keep logging enabled during this investigation; this revision registers its gift-bundle listener within the logging-enabled path.
No matching log line is a clue, not proof of a Twitch outage. An event can be ineligible under the configured rules, logging can be disabled, or the wrong run/file can be open. Twitch also documents that EventSub notifications can be delivered more than once, so matching records should be compared by event identity rather than merely by username.
Correct the clock once, then keep evidence
If an addition was missed, decide the intended remaining time and make one local correction. Avoid replaying the same event or restarting several copies of the app to force a credit. Preserve the relevant run's log before another rehearsal makes the timeline harder to follow.
For a useful bug report, include the build, event type, expected addition, actual addition, and a short sanitized record showing the decision. Logs can contain viewer identifiers and event payloads; remove unrelated personal data. An alert animation, a timer increment, and an OBS display update are three separate observations—recording each makes the failing stage much easier to identify.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.