WorkflowMax Outage History

WorkflowMax is up right now

WorkflowMax had 32 outages in the last 2 years totaling 57h 4m of downtime — averaging 1.3 incidents per month.

There were 32 WorkflowMax outages since June 10, 2024 totaling 57h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.workflowmax2.com

Minor July 21, 2024

Custom PDF Print Template - Fonts

Detected by Pingoru
Jul 21, 2024, 11:12 PM UTC
Resolved
Jul 22, 2024, 04:34 AM UTC
Duration
5h 22m
Affected: Web Application
Timeline · 4 updates
  1. investigating Jul 21, 2024, 11:12 PM UTC

    We are currently investigating an issue relating to Custom PDF Print Templates not formatting as desired due in some accounts due to using a different font than that in the .docx version of the template.

  2. identified Jul 21, 2024, 11:22 PM UTC

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

  3. monitoring Jul 22, 2024, 12:06 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 22, 2024, 04:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 18, 2024

API - Refresh Token Issue

Detected by Pingoru
Jul 18, 2024, 12:00 AM UTC
Resolved
Jul 18, 2024, 06:00 AM UTC
Duration
5h 59m
Affected: API (V1)
Timeline · 3 updates
  1. identified Jul 18, 2024, 01:20 AM UTC

    We are aware of an issue whereby some users are unable to refresh their access token. The cause has been identified and a fix is being implemented.

  2. monitoring Jul 18, 2024, 01:55 AM UTC

    A fix has been implemented and we are monitoring the results. If you are still encountering issues, we recommend attempting to vend a new token. If the issue persists, please contact support.

  3. resolved Jul 18, 2024, 06:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 12, 2024

Login - Too many redirects error

Detected by Pingoru
Jul 12, 2024, 02:00 PM UTC
Resolved
Jul 13, 2024, 11:45 PM UTC
Duration
1d 9h
Affected: Web Application
Timeline · 4 updates
  1. investigating Jul 12, 2024, 11:05 PM UTC

    We are currently investigating an issue where some users are reporting encountering a “too many redirects” error when attempting to sign in. If you encounter this error, we recommend you attempt to sign in after clearing your web browser’s cookies and cache. Instructions on how to do this for popular browsers: https://www.kaspersky.com/resource-center/preemptive-safety/how-to-clear-cache-and-cookies

  2. identified Jul 13, 2024, 02:20 AM UTC

    The issue has been identified and a fix is being implemented. In the meantime, if you encounter this error, we recommend you attempt to sign in after clearing your web browser’s cookies and cache. Instructions on how to do this for popular browsers: https://www.kaspersky.com/resource-center/preemptive-safety/how-to-clear-cache-and-cookies

  3. monitoring Jul 13, 2024, 11:22 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 13, 2024, 11:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 9, 2024

API - Authentication

Detected by Pingoru
Jul 09, 2024, 02:00 PM UTC
Resolved
Jul 09, 2024, 02:00 PM UTC
Duration
Affected: API (V1)
Timeline · 5 updates
  1. investigating Jul 09, 2024, 12:14 PM UTC

    We are currently investigating an issue whereby some API users are unable to authenticate successfully when making API calls and receive a 403 response unexpectedly.

  2. identified Jul 09, 2024, 12:29 PM UTC

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

  3. identified Jul 09, 2024, 12:29 PM UTC

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

  4. monitoring Jul 09, 2024, 12:50 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jul 09, 2024, 09:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 2, 2024

API - Degraded performance - POST/PUT Endpoints

Detected by Pingoru
Jul 02, 2024, 04:00 AM UTC
Resolved
Jul 02, 2024, 06:00 AM UTC
Duration
2h
Affected: API (V1)
Timeline · 4 updates
  1. identified Jul 02, 2024, 04:31 AM UTC

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

  2. identified Jul 02, 2024, 04:31 AM UTC

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

  3. monitoring Jul 02, 2024, 04:54 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 02, 2024, 11:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 17, 2024

Degraded Performance

Detected by Pingoru
Jun 17, 2024, 12:41 AM UTC
Resolved
Jun 17, 2024, 04:35 AM UTC
Duration
3h 54m
Affected: API (V1)Web Application
Timeline · 3 updates
  1. investigating Jun 17, 2024, 12:41 AM UTC

    We are currently investigating reports of degraded performance.

  2. monitoring Jun 17, 2024, 01:49 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 17, 2024, 04:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 10, 2024

API Service Unavailable (503 Response)

Detected by Pingoru
Jun 10, 2024, 10:22 PM UTC
Resolved
Jun 11, 2024, 04:24 AM UTC
Duration
6h 1m
Affected: API (V1)
Timeline · 3 updates
  1. investigating Jun 10, 2024, 10:22 PM UTC

    Some accounts are reporting encountering a 503 error unexpectedly. We are currently investigating this issue.

  2. monitoring Jun 11, 2024, 12:59 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 11, 2024, 04:24 AM UTC

    This incident has been resolved.

Read the full incident report →