[00:00] In this lesson, we'll take a look at quarantined items and see what we can do with them. I'm in the platform tab of my gateway viewing the store and forward engines page. When a record is placed into this quarantine, it means that the query was unable to execute successfully. Instead of repeatedly trying to run the query, it is placed here providing an opportunity to correct or remove the record. Let's move to the designer and attempt to create a quarantined item. What I have set up here is a transaction group that is recording this string value on my memory tag. Every time the string value changes, a new record will be added to the group table. What I'm going to do is something unexpected, which is changing the name of this table before the transaction group executes. So I'll run a query here to rename the table to GRP table. If we update the memory tag from, this is a string to this is my string, the transaction group will trigger and attempt to insert the string into the group table.

[01:05] This query will certainly fail as group table no longer exist. This typically wouldn't be an example of something you will run into, but for the purposes of this demonstration, it makes it easier to tell what's going on. If we go back to our gateway, now we can see our quarantine count updated to one. We can view more information by clicking on the more options button next to our engine here and select view details. Under quarantine management, we can see an entry for our quarantined item. The system recognizes that this came from a transaction group and we see the reason for failure is that group table does not exist. If we select this item, we'll get some options for handling the record. We can attempt to retry the query, but nothing would happen since group table still does not exist. Even if we do this however, the item will not be dropped from the quarantine, allowing for multiple attempts. We can delete the item, but then the data would be lost forever. The last option to export will download a JSON file of the data allowing us to fix it.

[02:04] When we open this up, we can see all of my data as well as the database table this is trying to write to. In my case, all I have to do is modify the name of the table the record is attempting to insert to. So I'm just going to change the name of this table to match the new table name. I'm going to save my file and I'll use this import quarantine file button to add the updated record. I'll go ahead and select the file and we should see this success message in the top right saying the quarantine item was imported. Let's go back to my designer and run this select query, and you can see that my database is updated with the new string. So if there's ever a problem in the store and forward with any of your data, you can always check the quarantine to see what the issue is, and then make your corrections.