Error logging being expanded for failed task triggers
New error logging is being added to the run engine and batch queue, which should significantly reduce the time spent debugging silent task failures.
5 team members · 13 developing stories
New error logging is being added to the run engine and batch queue, which should significantly reduce the time spent debugging silent task failures.
Developers can trace local execution by dropping temporary comment markers in the code, which are automatically stripped out before merge.
Developers can now back their AI SDK `useChat` hooks with Trigger.dev's durable execution, enabling long-running AI conversations that survive page refreshes and network drops.
Tasks that sit in the queue too long will soon be automatically discarded. A cascading time-to-live configuration system is being rolled out across global, task, and trigger levels to prevent outdated workloads from running.
A new compute workload manager should allow tasks to be paused and resumed using a dedicated compute gateway, freeing up resources during idle periods.
Expiration settings dictate how long a task should wait in the queue before it is automatically discarded, keeping time-sensitive operations relevant.
Administrators will soon be able to target specific users, projects, or organizations with context-aware alerts, keeping critical updates front and center without relying on email.
Documentation is being expanded to explain how to configure per-task middleware, allowing developers to set up context and locals for specific tasks without relying on global execution layers.
Documentation is being updated to clarify how scheduled tasks handle deduplication, warning developers that keys are scoped globally per project to prevent accidental environment overwrites.
Self-hosting documentation is being expanded to include critical environment variables for dedicated artifact storage, batch processing, and internal security secrets.
Developers will be able to pinpoint exactly which deployment versions are causing errors, using a new filter and a stacked bar chart visualization.
System administrators will be able to navigate directly to any execution run URL and instantly view it through the original user's perspective, accelerating support workflows.
Developers should have a clearer understanding of task limits, as the configuration is being updated to explicitly measure CPU compute time rather than total wall-clock duration.