This is more of an odd situation that doesn't occur every time but I decided to mention it in case someone else might be having the same issue.
At times the newly created incident gets applied to the incorrect component. I have tested this by purposely taking down a site and the majority of time it works as planned but once in a while I get the incident going astray.
Any one else seen or experienced this? I never received this prior to the latest release and I have double checked the component ID's in my config file with the ones applied when going to mysite/api/v1/components.
This is more of an odd situation that doesn't occur every time but I decided to mention it in case someone else might be having the same issue.
At times the newly created incident gets applied to the incorrect component. I have tested this by purposely taking down a site and the majority of time it works as planned but once in a while I get the incident going astray.
Any one else seen or experienced this? I never received this prior to the latest release and I have double checked the component ID's in my config file with the ones applied when going to mysite/api/v1/components.