3stepIT incident
Asset View API (AVA) problem affecting some integrations
3stepIT experienced a minor incident on February 15, 2019 affecting 3StepIT 3ConnectIT Service, lasting 79d 19h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Feb 15, 2019, 11:41 AM UTC
Asset view API (REST based device API) is affected in some cases where devices/assets are read from 3 Step IT's AssetNG device register based on changedata/changetime fields/columns. Changedate/changetime fields track when the device's information is last changed in AssetNG. The problem occurs if the device/asset is transferred under lease extension contract (leasing period is extended) in which case the changetime/changedate fields aren't updated correctly. The result is that the devices are next time transferred to customer systems through integration when some fields are updated either trough integration or AssetNG user interface. The issue is being handled by IT & development organization.
- resolved May 06, 2019, 07:10 AM UTC
The problem has been fixed, fix deployed and tested. Changetime/changedate are updated when the device status is changed, for example Active->In extension.