Request triggers, Task History may be slow to respond

This incident has been resolved.

We have resolved the issue in our systems at this time. We are continuing to monitor to ensure systems remain normal for any affected users.

We have identified elevated error rates affecting Request-triggered Workflows and Task History views. Our team is actively monitoring the situation.

We have resolved the issue in our systems at this time. We are continuing to monitor to ensure systems remain normal for any affected users.

We are continuing to investigate this issue and are working on a fix. At this time, this incident is still impacting a small number of total executions, and replaying the workflow may temporarily resolve any issues.

We are continuing to investigate this issue and have confirmed that its impact is limited to long-running workflow executions. Task History is not affected by this incident.

If you are impacted by this incident, you may see the following error in your workflow as a false positive: “Processing has failed repeatedly due to CPU and memory constraints on the server. Please either refactor your workflow to process less records or contact support.” Replaying the workflow may resolve the issue temporarily for that execution, but the fix we are working on will prevent any false positive occurrences for this error.

For almost all customers, this incident is affecting a small number of your total tasks (fewer than 1%). If we have identified your integrations as impacting a high volume of workflow executions, our team will reach out.

We will provide an update by end of day Saturday, December 14. If you have any questions or concerns, please reach out to your Customer Success Manager.

We are currently investigating an issue with our services that may be causing Request-triggered Workflows and Task History views to respond slowly.