TeamDynamix Outage History

Started Oct 28, 2026, 02:27 PM UTC· resolved Oct 28, 2026, 07:23 PM UTC

1. investigating Oct 28, 2026, 02:27 PM UTC

   We are currently investigating delays and increased error rates for Ticket Workflows

2. identified Oct 28, 2026, 03:16 PM UTC

   Work Management Ticket Workflows that contain iPaaS Flow Execution steps are not receiving communication of success or failure from iPaaS. After the configured timeout period for the iPaaS Flow Execution step (default of 30 minutes) the Ticket Workflow will check iPaaS for the flow execution status and continue to execute. This is causing delays in the processing of Ticket Workflows that include iPaaS Flow Execution steps.

3. monitoring Oct 28, 2026, 05:21 PM UTC

   A fix has been implemented and we are monitoring reductions of delays and error rates.

4. resolved Oct 28, 2026, 07:23 PM UTC

   We have confirmed the effectiveness of a hotfix to resolve this issue.

Read the full incident report →

Started Oct 16, 2026, 03:58 PM UTC· resolved Oct 28, 2026, 03:53 PM UTC

1. identified Oct 16, 2026, 03:58 PM UTC

   We have noticed delays and increased error rates in AI services for Work Management. This appears to stem from an Azure platform issue. We're taking actions to address it and will advise when values return to normal.

2. monitoring Oct 16, 2026, 07:16 PM UTC

   Azure has this issue marked as mitigated. We will monitor things to confirm they remain stable.

3. resolved Oct 28, 2026, 03:53 PM UTC

   This issue has not cropped up again relating to Azure's platform as a cause, so it is being marked as resolved.

Read the full incident report →

Started Oct 10, 2026, 08:55 AM UTC· resolved Oct 10, 2026, 03:09 PM UTC

1. investigating Oct 10, 2026, 08:55 AM UTC

   We're currently investigating delays and elevated errors in ticket workflows. We will follow up as we make progress on this issue.

2. resolved Oct 10, 2026, 03:09 PM UTC

   We have deployed hotfixes to address ticket workflow errors and delays in processing.

Read the full incident report →

Started Sep 18, 2026, 02:13 AM UTC· resolved Sep 18, 2026, 12:51 PM UTC

1. investigating Sep 18, 2026, 02:13 AM UTC

   We are currently investigating reports of elevated email monitor errors and attachment upload failures within Work Management.

2. monitoring Sep 18, 2026, 02:26 AM UTC

   We identified a capacity issue impacting the file system and successfully scaled the environment to address it. Email monitoring and attachment uploads are now functioning as expected.

3. resolved Sep 18, 2026, 12:51 PM UTC

   We identified and addressed a capacity issue impacting the file system by scaling the affected environment. Email monitoring and attachment uploads are now functioning normally, and all services have been restored. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Started Sep 09, 2026, 03:24 PM UTC· resolved Sep 09, 2026, 04:32 PM UTC

1. investigating Sep 09, 2026, 03:24 PM UTC

   We are actively investigating reports of performance degradation across Work Management the iPaaS platforms.

2. monitoring Sep 09, 2026, 03:31 PM UTC

   Performance appears to have fully returned to normal, however we will continue monitoring to ensure it remains stable. The root cause was a configuration change that had unintended side effects, which was quickly reversed.

3. resolved Sep 09, 2026, 04:32 PM UTC

   Confirmed as resolved, no further issues have risen since the stability changes were made.

Read the full incident report →

Started Aug 23, 2026, 05:03 AM UTC· resolved Aug 23, 2026, 06:47 AM UTC

1. investigating Aug 23, 2026, 05:03 AM UTC

   We are aware of a system offline message being returned for the work management web applications and are investigating root cause. The web applications appear online at this time.

2. resolved Aug 23, 2026, 06:47 AM UTC

   The work management web applications were offline from 11:56 p.m. Eastern Time on Saturday, August 22nd, to 12:54 a.m. Eastern Time on Sunday, August 23rd. The offline state was caused by a failure of the automation used to bring web servers back into the availability pool. We will not schedule any future activities that use this automation until it has been fixed.

Read the full incident report →

Started Jul 30, 2026, 03:46 PM UTC· resolved Jul 30, 2026, 05:54 PM UTC

1. investigating Jul 30, 2026, 03:46 PM UTC

   TeamDynamix is currently investigating reports of latency. We will provide updates as soon as possible.

2. resolved Jul 30, 2026, 05:54 PM UTC

   Slow/degraded loading of TDWorkManagement interface pages should be resolved as of now. An explanation of the root cause will be provided as soon as it is available, but we have seen performance levels return to normal for all partitions affected.

Read the full incident report →

Started Jul 07, 2026, 05:48 PM UTC· resolved Jul 07, 2026, 06:38 PM UTC

1. investigating Jul 07, 2026, 05:48 PM UTC

   TeamDynamix has been made aware of ongoing high-level Azure networking issue that are presently affecting all of our Azure hosting (Work Management and iPaaS) in East US. We will monitor and provide updates until Azure confirms this is resolved.

2. resolved Jul 07, 2026, 06:38 PM UTC

   Azure has confirmed this has been resolved at this time.

Read the full incident report →

Started Jun 10, 2026, 05:03 AM UTC· resolved Jun 10, 2026, 08:32 PM UTC

1. identified Jun 10, 2026, 05:03 AM UTC

   An upstream network issue is causing delays in connectivity to external systems for the Work Management platform.

2. monitoring Jun 10, 2026, 05:44 AM UTC

   As of 1:07AM ET traffic is flowing normally and backend services are processing the backlog.

3. resolved Jun 10, 2026, 08:32 PM UTC

   This issue was confirmed resolved as of 1:07AM ET on 6/10/2026. The upstream network issue has been resolved, and additional monitoring has been put in place to better capture the issue in the future.

Read the full incident report →

Started Jun 03, 2026, 03:50 PM UTC· resolved Jun 03, 2026, 08:41 PM UTC

1. investigating Jun 03, 2026, 03:50 PM UTC

   We are investigating an issue regarding the usage of the Web API to create tickets which results in specified custom attributes not having values set for them.

2. monitoring Jun 03, 2026, 06:58 PM UTC

   We are in the process of rolling out a hotfix for this issue, which we will monitor to confirm it has fully addressed the issue.

3. resolved Jun 03, 2026, 08:41 PM UTC

   At this time the rollout of the hotfix for the ticket creation API issue has completed. The fix has successfully addressed the issues reported regarding custom attributes on tickets being populated. This incident will be considered resolved.

Read the full incident report →

Started May 21, 2026, 08:07 PM UTC· resolved May 21, 2026, 09:19 PM UTC

1. investigating May 21, 2026, 08:07 PM UTC

   We are experiencing a backend service outage. We are working to identify the root cause and resolve as soon as possible.

2. monitoring May 21, 2026, 08:24 PM UTC

   The issue began at 3:45pm ET and a fix was deployed at 4:04pm ET. We are monitoring the effectiveness of the fix.

3. resolved May 21, 2026, 09:19 PM UTC

   All affected backend services are fully operational. A full post-mortem will be posted to the incident.

4. postmortem May 21, 2026, 09:19 PM UTC

   On May 21, 2026 from 3:45PM ET to 4:04PM ET \(19 minutes\), a TLS certificate used by internal backend services expired before being rotated, causing disruption to several back-end capabilities. The certificate has been renewed and all affected services are fully operational. **Impact** During the incident window, customers may have experienced: * **Outbound email delivery:** Emails sent from the platform during this window failed to send. * **iPaaS workflow steps:** iPaaS step types within ticket workflows failed to execute. * **Logging gaps:** Logging within the TeamDynamix Work Management application may have gaps during the incident window. **Root Cause** A TLS certificate used for internal service-to-service authentication reached its expiration date before being rotated. The expiration was not surfaced by our existing monitoring in time for the team to act. When the certificate expired, the affected services could no longer authenticate to dependent systems, producing the impact described above. **Resolution** The certificate was renewed and the affected services recovered automatically once trust was re-established. **Preventing Recurrence** We have expanded certificate expiry monitoring and alerting in our observability stack so that alerts trigger well in advance of expiration. We have also audited our existing certificate inventory to confirm no other certificates are at near-term risk. We're sorry for the disruption this caused. If you have questions about your specific environment, please reach out to our support team.

Read the full incident report →

Started May 18, 2026, 03:16 PM UTC· resolved May 21, 2026, 02:47 PM UTC

1. investigating May 18, 2026, 03:16 PM UTC

   Investigating client-licensed resource issues regarding access to interact with appropriate areas of Projects via the client portal. Client users are unable to add new issues and update tasks on project plans that they've been assigned to.

2. resolved May 21, 2026, 02:47 PM UTC

   A fix for the issues surrounding client portal interactions with project content was released last night and confirmed as addressing the problems in full. This is resolved at this point.

Read the full incident report →

Started Apr 06, 2026, 07:55 PM UTC· resolved Apr 06, 2026, 08:32 PM UTC

1. investigating Apr 06, 2026, 07:55 PM UTC

   We are investigating a delay in webhooks executions that began approximately around 2:14 PM ET. We're taking steps to mitigate the delays as soon as possible.

2. resolved Apr 06, 2026, 08:32 PM UTC

   As of 4:19 PM EST, webhooks are caught back up and processing as expected.

Read the full incident report →

Started Feb 04, 2026, 06:56 PM UTC· resolved Feb 05, 2026, 01:42 PM UTC

1. investigating Feb 04, 2026, 06:56 PM UTC

   TeamDynamix is currently investigating reports of latency and increased error rates. We will provide updates as soon as possible, though database reporting metrics appear to have returned to normal as of this time.

2. resolved Feb 05, 2026, 01:42 PM UTC

   After monitoring to confirm, performance has returned to normal as of last night. The issue was caused by higher than normal traffic levels for client portal resources.

Read the full incident report →

Started Jan 14, 2026, 06:40 PM UTC· resolved Jan 14, 2026, 07:08 PM UTC

1. investigating Jan 14, 2026, 06:40 PM UTC

   We are currently investigating an issue where email monitors are not draining as expected.

2. resolved Jan 14, 2026, 07:08 PM UTC

   IMAP email monitors were not processing in the East US environment from 12:00-1:45 ET. This issue is now resolved and email monitors are processing as expected.

Read the full incident report →

Started Jan 14, 2026, 05:57 PM UTC· resolved Jan 14, 2026, 07:24 PM UTC

1. monitoring Jan 14, 2026, 05:57 PM UTC

   We are currently investigating an issue that caused iPaaS to be unresponsive between 12:37PM ET to 12:48PM ET.

2. monitoring Jan 14, 2026, 06:04 PM UTC

   We are currently investigating an issue that caused some Work Management pages and iPaaS to be unresponsive between 12:37PM ET to 12:48PM ET.

3. resolved Jan 14, 2026, 07:24 PM UTC

   The U.S. tenant of iPaaS/CAI had a brief moment of UI unavailability, and flows responding with 502 bad gateway error codes between 12:37PM ET and 12:48PM ET. This issue is now resolved.

Read the full incident report →

Started Dec 16, 2025, 04:05 PM UTC· resolved Dec 17, 2025, 06:50 PM UTC

1. investigating Dec 16, 2025, 04:05 PM UTC

   We are currently investigating reports of performance degradation around the iPaaS user interface page loads. At this time iPaaS flows are executing at expected levels and remain fully operational.

2. monitoring Dec 16, 2025, 06:16 PM UTC

   Shortly after this issue arose we did see performance levels return quickly to expected metrics. At this time we will continue monitoring as the root cause is diagnosed, but the web interface should be completely operational based on present measurements.

3. resolved Dec 17, 2025, 06:50 PM UTC

   A high-memory usage scenario caused a brief period of slowness within the UI. We were able to isolate the instance and restart which resolved the UI slowness by 11am EST yesterday. We are currently evaluating options to prevent this behavior in the future.

Read the full incident report →

Started Dec 06, 2025, 02:25 AM UTC· resolved Dec 06, 2025, 02:41 AM UTC

1. investigating Dec 06, 2025, 02:25 AM UTC

   We are currently investigating reports of unhandled errors when accessing tickets in Work Management.

2. resolved Dec 06, 2025, 02:41 AM UTC

   We’ve deployed a fix to address unhandled errors when accessing tickets in Work Management. The issue was caused by a misconfiguration during a maintenance deployment and has now been fully resolved.

Read the full incident report →

Started Nov 22, 2025, 07:10 AM UTC· resolved Nov 25, 2025, 02:35 PM UTC

1. investigating Nov 22, 2025, 07:10 AM UTC

   We have noticed an increased error rate in the loading of charts and are investigating.

2. resolved Nov 25, 2025, 02:35 PM UTC

   We have released a hotfix that resolved the bug that caused this issue.

Read the full incident report →

Started Nov 12, 2025, 08:04 PM UTC· resolved Nov 13, 2025, 05:08 PM UTC

1. investigating Nov 12, 2025, 08:04 PM UTC

   We have noticed instances of increased response times and are taking corrective efforts to reduce those to normal levels. We'll provide updates here as they are available.

2. resolved Nov 13, 2025, 05:08 PM UTC

   Hotfixes have been implemented to address elevated response times caused by processing the backend data for dashboard widgets. We have observed performance returned to normal levels as of about 11:20 AM ET.

Read the full incident report →

Started Nov 12, 2025, 04:12 PM UTC· resolved Nov 12, 2025, 06:07 PM UTC

1. investigating Nov 12, 2025, 04:12 PM UTC

   We are currently investigating and taking steps to address reports of increased response times in WorkManagement, mainly centered around dashboard interaction/load times.

2. resolved Nov 12, 2025, 06:07 PM UTC

   We have resolved the dashboard-related instances of response time elevation issues.

Read the full incident report →

Started Nov 10, 2025, 02:41 PM UTC· resolved Nov 10, 2025, 09:31 PM UTC

1. investigating Nov 10, 2025, 02:41 PM UTC

   We are currently investigating reports of performance degradations.

2. investigating Nov 10, 2025, 02:50 PM UTC

   We are continuing to investigate this issue.

3. identified Nov 10, 2025, 04:08 PM UTC

   Thank you for your continued patience. We have identified the issue and are actively working to develop a fix for the Work Management performance degradation. We'll continue to provide updates as we know more about estimated resolution time.

4. monitoring Nov 10, 2025, 05:08 PM UTC

   A fix has been deployed for Work Management performance degradation. Pages should begin to load. We are still actively monitoring and will continue to communicate updates.

5. monitoring Nov 10, 2025, 05:58 PM UTC

   We want to provide an update regarding the performance issues affecting our application. As shared earlier, we deployed a fix intended to resolve the degradation. Unfortunately, the fix did not produce the expected improvements, and we are still seeing performance challenges. Our team is actively investigating the issue with high priority. We are exploring additional solutions and working diligently to identify and address the root cause. We understand how critical our service is to your operations and deeply regret the inconvenience this is causing. We will continue to keep you informed with regular updates and will notify you as soon as we have more information or a confirmed resolution. Once we restore service, we will provide additional information on root cause.

6. monitoring Nov 10, 2025, 08:12 PM UTC

   We continue to work on the issue causing degraded performance in TeamDynamix Work Management. We sincerely apologize for the inconvenience and appreciate your patience. Our team is working around the clock to restore full service as quickly as possible. Once service is fully restored, we will share additional details regarding the root cause.

7. resolved Nov 10, 2025, 09:31 PM UTC

   We’ve resolved the issue that was causing degraded performance in TeamDynamix Work Management, and full service has now been restored. We appreciate your patience and understanding during this time. Our team is continuing to investigate the root cause and will share additional details once the post-incident review is complete. We are also actively monitoring the system to ensure everything remains stable and continues to run smoothly. Thank you for your continued support.

8. postmortem Nov 14, 2025, 02:24 PM UTC

   ## **Postmortem Report Available: TeamDynamix Work Management Performance Incident on November 10, 2025** Regarding the performance incident which occurred on Monday, November 10, 2025, a detailed explanation of the root cause, the corrective actions taken, and preventative steps to minimize the risk of recurrence can be found in the Knowledge Base article linked below. [2025-11-10 Performance Incident - TeamDynamix Work Management 12.1 Release](https://solutions.teamdynamix.com/TDClient/1965/Portal/KB/ArticleDet?ID=169492) Thank you for your patience and continued understanding. If you experience any issues or have additional questions, please do not hesitate to contact our support team via our [Client Portal](https://solutions.teamdynamix.com).

Read the full incident report →

Started Nov 08, 2025, 10:36 AM UTC· resolved Nov 17, 2025, 05:09 PM UTC

1. identified Nov 08, 2025, 10:36 AM UTC

   We have identified an issue with the linkage between Work Management and iPaaS that could cause issues with the ChatBot loading on Client Portal and the error message "A fatal error was encountered. Message: The Customer ID must be a valid GUID format. Please verify the Customer ID from your TeamDynamix Automation Platform settings." on iPaaS flow runs. We are working on a permanent fix for this issue. We have found that resaving the Integration Settings at TDAdmin -> Organization Setttings -> TeamDynamix Automation Settings -> Integration Settings is a viable workaround to restore service immediately.

2. identified Nov 08, 2025, 01:09 PM UTC

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

3. identified Nov 08, 2025, 01:37 PM UTC

   WORKAROUND: To resolve the issue, locate the Customer ID and Secret in the AI and Automations (iPaaS) environment by going to the Administration Menu > Service Accounts and opening the service account used for your TeamDynamix environment. Account ID maps to Customer ID, and Primary Secret maps to Client Secret. Copy those values into TDAdmin > Organization Settings > TeamDynamix Automation Settings -> Integration Settings and hit save.

4. monitoring Nov 08, 2025, 03:26 PM UTC

   ACTION REQUIRED: As part of the 12.1 release, we performed a cutover to update all Microsoft Teams integrations. During this process, the update was inadvertently applied to all integration types, including: - Bomgar - Microsoft Teams - Slack - TeamDynamix iPaaS - Microsoft Intune This caused the settings for all integrations except Microsoft Teams to become corrupted. To restore full functionality, the settings for the following integrations will need to be re-enabled: - Bomgar: https://solutions.teamdynamix.com/TDClient/1965/Portal/KB/ArticleDet?ID=9244 - Slack: https://solutions.teamdynamix.com/TDClient/1965/Portal/KB/ArticleDet?ID=115017 - TeamDynamix iPaaS: https://solutions.teamdynamix.com/TDClient/1965/Portal/KB/ArticleDet?ID=115872 - Microsoft Intune: https://solutions.teamdynamix.com/TDClient/1965/Portal/KB/ArticleDet?ID=161834 We apologize for the inconvenience. If you have trouble re-enabling any of the integrations, please reach out to our support team for further assistance: https://solutions.teamdynamix.com/TDClient/1965/Portal/Requests/ServiceDet?ID=2147

5. monitoring Nov 11, 2025, 03:01 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Nov 17, 2025, 05:09 PM UTC

   This was a notice of affected integrations rather than an ongoing incident.

Read the full incident report →

Started Nov 08, 2025, 09:08 AM UTC· resolved Nov 08, 2025, 01:09 PM UTC

1. investigating Nov 08, 2025, 09:08 AM UTC

   The 12.1 production upgrade is live for the majority of the system. We are still processing a cutover which impacts the following services: Item Alerts, KB Article Review Reminders, Project Health Updates, Report Delivery, RSS Feeds, Source Control Events, Ticket SLAs and Ticket Workflow Web Service Steps. We will continue to provide updates as the cutover progresses.

2. resolved Nov 08, 2025, 01:09 PM UTC

   The 12.1 cutover is complete and backend services are now running again.

Read the full incident report →

Started Nov 06, 2025, 06:47 PM UTC· resolved Nov 06, 2025, 07:50 PM UTC

1. investigating Nov 06, 2025, 06:47 PM UTC

   We are currently investigating reports of performance degradation.

2. monitoring Nov 06, 2025, 07:30 PM UTC

   TeamDynamix performance has returned to normal levels as of 1:51 eastern. It began around 1:31 eastern. We are investigating the root cause and will post that here when available.

3. resolved Nov 06, 2025, 07:50 PM UTC

   Incident is resolved. We are continuing to investigate the root cause and will provide that when it is available.

Read the full incident report →