Torq Status

Resolved: We successfully replicated all activity log data starting on August 18th 00:00 (UTC) Activity log data replication continues until 90 days of data is available to query, which is expected in the coming days. As mentioned in former updates, live activity log data is ingested normally without issues

Due to the above, we are marking this incident as resolved.

Monitoring: Ongoing activity log events are being ingested as usual, with no performance impact. Replicating historical Activity Log data from before the incident is still ongoing. No data was lost during the incident.

Monitoring: Ongoing activity log events are being ingested as usual, with no performance impact. Activity log data from before the incident is still incomplete, and is being re-ingested. No data was lost during the incident.

Another update will be made once we have an ETA for showing the incomplete data in the UI.

Monitoring: * New executions are now showing up on the activity log. Backlog ingestion (last ~10 hours) is still in progress.

• All Events JSON events are now shown in the activity log, though the associated execution may still be missing.
• Execution logs in canvas are working and show full history for all steps.

We'll update once we have an ETA for showing activity log data from before the incident. No events are lost — all activity logs will be restored.

We'll continue posting updates until this is fully resolved.

Monitoring: New executions are now showing up on the activity log. Backlog ingestion (last ~10 hours) is still in progress, and event-attachment to cases will work going forward from now on.

We don't yet have an ETA for when backlog ingestion will finish or when older events will be visible in the UI. We'll share an ETA as soon as we have one.

We'll continue posting updates until this is fully resolved.

Identified: The backlog queue continues to be ingested. Event-attachment to cases should start working again as processing catches up. We're currently working through the backlog for the last 10 hours of data.

Known limitation: Older events (before the incident) are not currently visible in the UI while this backlog is processed.

We'll continue to post updates as we make progress toward full resolution.

Identified: The backlog of activity log data has started being ingested, and we're seeing queue processing resume. Workflow event-attachment failures related to this issue should begin to ease as the backlog clears.

We're continuing to monitor closely and will share a full ETA for complete resolution when possible.

We appreciate your patience as we work through this.

Identified: We're aware of an issue affecting activity log ingestion, causing delays in log processing and failures when workflows attempt to attach events to cases. This is impacting a subset of customers in US data center.

We're treating this as a top priority and working it with all hands on deck. We'll post the next update ASAP.

We apologize for the disruption and appreciate your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating delayed ingestion for activity logs.

Some customers may experience a delay in activity log data appearing in the platform.

Resolved: We successfully replicated all activity log data starting on August 18th 00:00 (UTC) Activity log data replication continues until 90 days of data is available to query, which is expected in the coming days. As mentioned in former updates, live activity log data is ingested normally without issues

Due to the above, we are marking this incident as resolved.

Monitoring: Ongoing activity log events are being ingested as usual, with no performance impact. Replicating historical Activity Log data from before the incident is still ongoing. No data was lost during the incident.

Monitoring: Ongoing activity log events are being ingested as usual, with no performance impact. Activity log data from before the incident is still incomplete, and is being re-ingested. No data was lost during the incident.

Another update will be made once we have an ETA for showing the incomplete data in the UI.

Monitoring: * New executions are now showing up on the activity log. Backlog ingestion (last ~10 hours) is still in progress.

• All Events JSON events are now shown in the activity log, though the associated execution may still be missing.
• Execution logs in canvas are working and show full history for all steps.

We'll update once we have an ETA for showing activity log data from before the incident. No events are lost — all activity logs will be restored.

We'll continue posting updates until this is fully resolved.

Monitoring: New executions are now showing up on the activity log. Backlog ingestion (last ~10 hours) is still in progress, and event-attachment to cases will work going forward from now on.

We don't yet have an ETA for when backlog ingestion will finish or when older events will be visible in the UI. We'll share an ETA as soon as we have one.

We'll continue posting updates until this is fully resolved.

Identified: The backlog queue continues to be ingested. Event-attachment to cases should start working again as processing catches up. We're currently working through the backlog for the last 10 hours of data.

Known limitation: Older events (before the incident) are not currently visible in the UI while this backlog is processed.

We'll continue to post updates as we make progress toward full resolution.

Identified: The backlog of activity log data has started being ingested, and we're seeing queue processing resume. Workflow event-attachment failures related to this issue should begin to ease as the backlog clears.

We're continuing to monitor closely and will share a full ETA for complete resolution when possible.

We appreciate your patience as we work through this.

Identified: We're aware of an issue affecting activity log ingestion, causing delays in log processing and failures when workflows attempt to attach events to cases. This is impacting a subset of customers in US data center.

We're treating this as a top priority and working it with all hands on deck. We'll post the next update ASAP.

We apologize for the disruption and appreciate your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating delayed ingestion for activity logs.

Some customers may experience a delay in activity log data appearing in the platform.