Conditional Tally connector launcher

The problem

TallyDataConnector would only work when tally.exe was already running. Forgetting that step meant failed syncs, broken reports, and a daily "is Tally open?" check from whoever was on data duty. It also meant exposing Tally to background processes when it didn't need to be.

The solution

A small launcher script that checks for tally.exe first and only starts TallyDataConnector when Tally is actually live — and shuts it down cleanly when Tally exits.

• Polls process list for tally.exe at boot and at intervals
• Conditionally launches TallyDataConnector only when Tally is running
• Auto-stops the connector when Tally is closed (no orphan processes)
• Runs silently in the background — no popups, no user input
• Logs every state change for debugging

The outcome

• Manual "is Tally open?" checks eliminated — runs as a background service
• Zero failed syncs since deployment — connector only ever starts when it should
• No orphan processes — connector cleans itself up on Tally exit

Tech stack

Note for Harsh: confirm exact tooling (PowerShell vs batch vs Python) and update the list.

Have a Tally workflow that breaks?

Most Tally pain is solvable with TDL or a small launcher script. Tell us what's breaking.