SnapLogic incident

SnapLogic Scheduled Tasks Interruption

Notice Resolved View vendor source →

SnapLogic experienced a notice incident on December 29, 2020 affecting Intelligent Integration Platform, lasting 8d 2h. The incident has been resolved; the full update timeline is below.

Started
Dec 29, 2020, 12:33 AM UTC
Resolved
Jan 06, 2021, 02:41 AM UTC
Duration
8d 2h
Detected by Pingoru
Dec 29, 2020, 12:33 AM UTC

Affected components

Intelligent Integration Platform

Update timeline

  1. investigating Dec 29, 2020, 12:33 AM UTC

    Investigating: We have recently detected an issue affecting scheduled tasks for the week of December 28th - December 31st, 2020 on the SnapLogic platform. Weekly scheduled tasks that are scheduled to execute during the week of December 28 - December 31 will not execute on these days. Regularly scheduled weekly executions should start again on January 1. Monthly and yearly tasks that are scheduled to run in January are also impacted and may miss their January execution. Our team is actively investigating the cause and working to resolve the issue. The following scheduled tasks may be affected: -Weekly Scheduled Task Execution scheduled for 12/28/20-12/31/20 -Monthly Scheduled Task Execution scheduled for on/after 01/01/21 -Yearly Scheduled Task Execution scheduled for on/after 01/01/21

  2. monitoring Jan 05, 2021, 03:53 AM UTC

    SnapLogic’s Scheduled Task Issue is no longer occurring. As of Jan 4th 12:00 AM UTC, the scheduling issue that occurred due to the 53rd calendar week in 2020 is no longer occurring. SnapLogic is working on a resolution which will be deployed after undergoing regression testing. This incident will continue to be monitored until Tuesday Jan 5th 2021 5:00 PM PDT, at which time it will then be marked as closed. The resolution will be deployed in due course. The next occurrence of a 53rd week is in 2026 which should not result in any concerns once this update has been deployed.

  3. monitoring Jan 05, 2021, 04:12 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jan 06, 2021, 02:41 AM UTC

    This incident has been resolved.