Knowledgebase Article Number

360037905354

Description

Published November 5th, 2019, at approximately 1 p.m. EST. 
Last updated on November 5th, 2019.

Resolution 

At Bastian Solutions, we continually strive to provide superb customer service at the highest standard, and not only reactive but proactive support. Transparency is a key component in helping achieve this objective and with that in mind, we are providing a full root cause analysis for the disruptions in service on October 28th – October 29th, 2019 described below.
 

Summary:

11:44 PM EST
The client notified Bastian Outbound Pallet builds were giving an error message 

12:48 AM EST
Bastian restarted All services and the entire App server. Auto pack began working, but outbound pallet still gave an error. Site stated they were done for the night

8:31 AM EST
Nathan created internal ticket and began investigation

9:15 AM EST
Will Saucer engaged and assisted in investigation. 

9:45 AM EST

Started comparing tables and missing fields that existed in Test but not production. Located missing Container type

9:47 AM EST
Container type 0 had an incorrect container category

Root Cause:

Container type 0 which is Exacta Default container type had an incorrect container category

Resolution:

Corrected the incorrect container category for container type 0 in the table

Next Steps and Preventive Actions:

Bastian will work with DBA's and on site resources to identify critical system tables and add either audit journals or delta tables. Bastian will investigate current tools available to SKF team to determine if this could have been modified by site resource.

Our commitment to you:

Bastian Solutions understands the impact of the disruption that occurred and affected operations for your organization. It is our primary objective in providing our clients with superb customer service and we assure you we're taking the required preventative measures to prevent reoccurrence.