{"article":{"id":36773331069207,"url":"https://plaid.zendesk.com/api/v2/help_center/en-us/articles/36773331069207.json","html_url":"https://support.plaid.com/hc/en-us/articles/36773331069207-What-do-the-Known-Issue-statuses-mean","author_id":396033157154,"comments_disabled":true,"draft":false,"promoted":false,"position":4,"vote_sum":0,"vote_count":0,"section_id":36773288000023,"created_at":"2025-12-04T10:50:06Z","updated_at":"2026-05-31T19:17:50Z","name":"What do the Known Issue statuses mean?","title":"What do the Known Issue statuses mean?","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-05-31T19:17:50Z","user_segment_id":null,"permission_group_id":1121794,"content_tag_ids":[],"label_names":[],"body":"<p>Each issue has a status that reflects the state of the internal escalation. More information on each status is below:</p>\n<ul>\n<li>\n<strong>Reported</strong> - the issue has been documented, but engineering has not reviewed it yet</li>\n<li>\n<strong>Awaiting Resolution</strong> - engineering has reviewed the issue, and it is under consideration for a fix</li>\n<li>\n<strong>Awaiting Migration</strong> - engineering has identified that the issue will be addressed in a rebuild of the integration, but this has not started</li>\n<li>\n<strong>Migration In Progress</strong> - engineering has identified that the issue will be addressed in a rebuild of the integration that is currently in development</li>\n<li>\n<strong>Gathering Data</strong> - engineering is collecting additional information to understand and address the issue</li>\n<li>\n<strong>Escalated to Data Partner</strong> - engineering has escalated this issue to the financial institution for further investigation</li>\n<li>\n<strong>Requires Data Partner Resolution</strong> - engineering is attempting to contact the financial institution for further investigations but have not yet made contact</li>\n<li>\n<strong>Needs Data Partner Escalation</strong> - engineering is reaching out to the financial institution for further investigation</li>\n<li>\n<strong>Scheduled</strong> - engineering has scheduled the issue for review</li>\n<li>\n<strong>Fix in Progress with Data Partner</strong> - engineering has reached out to the financial institution, which is working on a fix</li>\n<li>\n<strong>Fix in Progress</strong> - engineering is currently working on a fix for the issue</li>\n<li>\n<strong>Fix Pending Validation</strong> - engineering has identified a fix which is being validated before deployment</li>\n<li>\n<strong>Not Prioritized</strong> - engineering has determined they will not fix the issue due to low impact</li>\n<li>\n<strong>Duplicate</strong> - engineering has marked this as a duplicate of another issue that has been raised</li>\n<li>\n<strong>Expected Behavior</strong> - engineering has confirmed that the reported behavior is working as intended or is a documented limitation</li>\n<li>\n<strong>Resolved</strong> - The issue has been fixed by our engineering team, or they no longer see the issue in our logs</li>\n<li>\n<strong>Cannot Fix</strong> - The issue cannot be fixed due to technical or business constraints</li>\n</ul>","user_segment_ids":[]}}