infinity load when sync github issue
ART-2992_KNOWLEDGE_NODE-26
[GitHub PAT](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) with the account that will be used to set up the AirSync.\n\n   The minimum required permissions are READ + WRITE Issues and READ + WRITE Pull Requests.\n2. Go to **Settings** > **Integrations** > **Snap-ins** and install **GitHub Issues**.\n\n   If there are any existing **GitHub Issues** already added, **Add** the other.\n3. Under **Settings** > **Integrations** >
GitHub Issues AirSync | AirSync | Snap-ins | DevRev
ART-17711_KNOWLEDGE_NODE-1
access.\n\nOnce Person A was re-added with the right permissions, the retry worked again.\n\nIf this happens, check who started the sync and make sure that person still exists in the org and has the right permissions. Until ownership handling is improved, retries for syncs started by users without access will fail with similar 401 or 403 errors.'
Sync fails when original sync owners loses permissions
ART-17711_KNOWLEDGE_NODE-0
b'We ran into a case where an AirSync was started by one person (Person A) and later failed. Another user (Person B) tried to click Retry, but it didn\xe2\x80\x99t work. The logs showed 401 and 403 errors in communication between the snap-in and the snap-in manager.\n\nIt turned out that AirSync assigns the sync owner to whoever started it. Since Person A had been removed from the org or lost permissions, the retry failed \xe2\x80\x94 the system still expected the original owner to have valid
Sync fails when original sync owners loses permissions
ART-2992_KNOWLEDGE_NODE-28
AirSyncs\n\nTo view currently running and previous AirSyncs from various sources, do the following:\n\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\n2. Select the import you want to view.\n3. Select the context menu (\xe2\x8b\xae) > **View Report**.\n\n### Periodic sync\n\nAfter successfully importing to DevRev, you have the option to enable a periodic sync. This allows for automatic synchronization with DevRev on a regular basis. By default, the sync occurs once an hour.\n\nTo
GitHub Issues AirSync | AirSync | Snap-ins | DevRev
ART-17222_KNOWLEDGE_NODE-1
data loading by sending a message with the event type `START_LOADING_DATA` to the snap-in.\n\nIf the maximum AirSync snap-in runtime (13 minutes) has been reached,\nthe snap-in must respond to AirSync with a message with event type of `DATA_LOADING_PROGRESS`, together with an optional progress estimate.\n\nIn case of `DATA_LOADING_PROGRESS`, AirSync starts the snap-in with a message with event type `CONTINUE_LOADING_DATA`.\n\nOnce the data extraction is done, the snap-in must respond to AirSync
Load data | DevRev | Docs
ART-17219_KNOWLEDGE_NODE-18
|\n| 13 | "category":"issue" |\n| 14 | }, |\n| 15 | "comments":{ |\n| 16 | "name":"Comment" |\n| 17 | } |\n| 18 | }, |\n| 19 | "record_type_categories":{ |\n| 20 | "issue":{ |\n| 21 | "are_record_type_conversions_possible":true |\n| 22 | } |\n| 23 | } |\n| 24 | } |\n```\n\n[5](/airsync/metadata-extraction#mark-record-types-as-loadable)\n\n### Mark record types as loadable\n\nThe record types that will be used in a 2-way sync must be marked with `is_loadable`.\nThis will allow AirSync to load
Metadata extraction | DevRev | Docs
ART-17221_KNOWLEDGE_NODE-19
SDK\xe2\x80\x99s `adapter` object.\n\n```\n|  |  |\n| --- | --- |\n| 1 | adapter.state["users"].completed = true; |\n```\n\nA snap-in must consult its state to obtain information on when the last successful forward sync started.\n\n* The snap-in\xe2\x80\x99s `state` is loaded at the start of each invocation and saved at its end.\n* The snap-in\xe2\x80\x99s `state` must be a valid JSON object.\n* Each sync direction (to DevRev and from DevRev) has its own `state` object that is not shared.\n*
Data extraction | DevRev | Docs
ART-8442_KNOWLEDGE_NODE-25
the legacy Airdrop are discouraged\n\n  * The legacy Airdrop will be removed in the coming weeks\n\n**Migration path**\n\nTo upgrade, delete your existing GitHub Airdrop unit and create a new one using the latest version.\n\nFor detailed information, visit our [GitHub Airdrop documentation](/docs/integrations/github-airdrop).\n\n### Airdrop Integrations\n\nZendesk articles imported via Airdrop now include additional sync metadata, such as external reference, origin system, and sync date. This
January 2025 | Changelog | DevRev