workflow sync account information failing for ticket TKT-22357
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-17359_KNOWLEDGE_NODE-6
frequency settings\n\nCheck if partial reimports are running frequently\n\nWorkflows are not triggered?\n\nCheck if triggers are enabled for your periodic sync in Settings > Integrations > AirSync > [sync unit] > Settings\n\nVerify sync was a periodic sync and not manual or initial.\n\nVerify the sync completed'
AirSync Notifications and Workflows
ART-2044_KNOWLEDGE_NODE-26
Problem | Ticket | \xe2\x9c\x85 | \xe2\x9c\x85 |\n| Comment on Case/Task/Incident/Problem | Comment on Ticket | \xe2\x9c\x85 | \xe2\x9c\x85 |\n| Attachment on Case/Task/Incident/Problem | Attachment on Ticket | \xe2\x9c\x85 | \xe2\x9c\x85 |\n| Account | Account | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Contact | Contact | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Consumer | Contact | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Agent | DevUser | \xe2\x9c\x85 | \xe2\x9d\x8c |\n\nTo ease the transition from ServiceNow
ServiceNow AirSync | AirSync | Snap-ins | DevRev
ART-2049_KNOWLEDGE_NODE-25
of Freshdesk objects and their corresponding DevRev\nequivalent. Those marked as **Supported** are eligible for AirSync.\n\n| Freshdesk Object | DevRev Object | Sync to DevRev | Sync to Freshdesk |\n| --- | --- | --- | --- |\n| Ticket | Ticket | \xe2\x9c\x85 | \xe2\x9c\x85 |\n| Company | Account | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Contact | Customer | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Agent | DevUser | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Conversation | Timeline Comment | \xe2\x9c\x85 | \xe2\x9c\x85
Freshdesk AirSync | AirSync | Snap-ins | DevRev