Skip to content
GTM Tech News
Back to All news

HockeyStack improves scheduled and triggered Workflows reliability

HockeyStack updated scheduled and triggered Workflows for reliability and revamped the Workflows list with run status and next scheduled time.

Image: HockeyStack press materials, from the announcement

HockeyStack's March 23, 2026 release notes describe a push to improve the reliability and performance of its Workflows feature. According to the company, scheduled workflows now run more consistently and fire on time without delays. Triggered workflows are better at detecting the right data, including picking up new records, capturing changes between runs and firing across more scenarios. HockeyStack also revamped the Workflows list page to show whether each workflow is triggered or scheduled, when it is next scheduled to run and the status of its last run. The company says it is actively monitoring performance after the changes.

The details

  • Scheduled workflows were updated to fire on time more consistently.
  • Triggered workflows now detect new records and changes between runs more reliably.
  • The Workflows list page shows triggered versus scheduled type, Next Scheduled At and Last Run Status.
  • The release notes do not list new workflow actions or destinations.

Context

This release followed a run of HockeyStack updates in our coverage: Blueprints 1.0 (January 12, 2026), Agents with 14 prebuilt templates (January 26, 2026) and Meetings and AI-prioritized Tasks views for Agents (February 9, 2026). The next release notes in our coverage, on September 30, 2026, introduced an MCP for querying data and building reports through AI.

Not disclosed

  • Specific performance or uptime figures
  • What caused the earlier delays
  • Whether any workflow limits changed by plan
Discuss this with peers in the ForgeX Community
Announcement type
Feature update
Release notes from HockeyStack, published Mar 23, 2026
docs.hockeystack.com
Added to GTM Tech News on Mar 23, 2026. Written up by ForgeX from the source; the vendor did not review it.
Open
Report an error

Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.

cora@forgex.ai