Task Started but Stop Is Not Created

Created by TeamTrace Support, Modified on Tue, 15 Sep at 5:41 AM by TeamTrace Support

Scenario

Customer assumes:

"When an employee starts a task, TeamTrace should create a Stop."

Resolution

Explain that these are separate concepts.


Task

Represents work performed against an assigned task.


Stop

Represents a location-based event.


Punch In/Out

Represents attendance/work-session events.


Timeline

Combines relevant activity into a chronological view.

TeamTrace's August 2025 release notes explicitly describe these separately.


Troubleshooting

Check:

  1. Task start time.
  2. Task end time.
  3. Employee location.
  4. Stop duration.
  5. Route.
  6. Network status.
  7. Last Sync.

If the employee never met the Stop detection conditions, a Stop may not appear.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article