In this guide
- "Still running" means the tag started and has not called its completion callback.
- In server containers the usual cause is a vendor request that is slow or never answers. In web containers it is a callback that never fires or a tag sequence that waits.
- Add timeouts, check the vendor and test the request on its own.
Most tags finish in milliseconds. When one stays at "Still running" in Preview, the container is waiting for it. This page covers what that waiting usually is, and how to fix it, in server and web containers. The related error state is covered in tag status failed.
Server container causes
data.gtmOnSuccess() or data.gtmOnFailure() in some branch.Runs on your domain, anywhere
Your tracking runs on your own domain, so a visit from any country is handled the same way.
Web container causes
gtmOnSuccess or move the script into a template.How to debug
Reproduce in Preview
Note which tag stays running.
Look at the tag details
The outgoing request, if any, and whether a response arrived.
Test the endpoint alone
Use a tool outside the container to see if the vendor answers.
Add a timeout in the template
Fail the tag after a set time so it does not hang the container.
Retest
Confirm it moves to fired or failed.
Check your tracking in one pass
This is an example. Run the check on your own site to see where yours stands.
A worked example
A server tag that sends events to a CRM webhook stays at running for a minute and then times out. Opening the outgoing request shows the webhook URL has a typo, so the connection hangs. After correcting the URL the tag finishes in under a second. A timeout in the template would have turned the hang into a clear failure in a few seconds.
Terms you will see
- Callback
- A signal a tag sends when it has finished.
- gtmOnSuccess
- The call that tells Tag Manager the tag finished well.
- gtmOnFailure
- The call that tells Tag Manager the tag ended with an error.
- Timeout
- A limit after which waiting stops.
- Tag sequencing
- A rule that one tag must finish before another starts.
A quick decision list
| What you see | Likely cause | First action |
|---|---|---|
| Server tag running for a long time | Vendor slow | Open the request in Preview and test the URL elsewhere |
| Web tag running, no request visible | Callback never called | Check the template or custom HTML |
| All tags after one stay queued | Setup tag unfinished | Check tag sequencing |
| Only on some pages | A consent or page condition | Compare the page with a working one |
How to avoid it next time
Give every template path a clear ending, set a timeout on every outgoing request, and keep a short list of the vendors your container depends on, with the link to each status page. When a tag hangs, open that list first. A few minutes of preparation turns a mysterious delay into a known cause, and it lets you tell the team quickly whether the issue is inside your container or on the vendor's side.
Terms you will see
- Running
- The tag has started and not reported that it finished.
- Fired
- The tag finished successfully.
- Timeout
- The time after which waiting stops.
- Promise
- A programming object that represents a result that will come later.
- Tag sequencing
- A setting that makes one tag wait for another.
Watch events arrive, live
A sample feed. In Open Tracked you see the same stream for your own store.
Frequently asked questions
What does "still running" mean?
The tag started but has not reported that it finished. It is waiting for a response or a callback.
Why do server tags hang?
Usually a slow or unreachable vendor, a wrong URL, or a template that does not call its completion callback.
Is it the same as failed?
No. Failed means it ended with an error. Still running means it has not ended.
Can a delay power-up cause it?
A delay holds the request on purpose for the time you set. Check whether the rule applies to the path.
How do I stop a tag from hanging?
Add a timeout and make sure every code path calls success or failure.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Troubleshooting · 6 min read
