Integration Logs

opening the integration logs viewer each integration card in settings integrations shows a synced x minutes ago label below the integration name for integrations that support detailed logging, this label is now clickable click it to open the integration logs viewer, a modal scoped to that integration type from there, you can drill down through every sync run, see which records succeeded or failed, and follow individual api calls all the way to the response status returned by the third party tool the viewer is always scoped to the integration you clicked on, so opening it from the hubspot card shows only hubspot runs, opening it from chargebee shows only chargebee runs, and so on not every integration supports detailed logging on day one the click to open behavior only appears on cards where logs are available drilling down through a sync run the viewer follows a five level structure, with a breadcrumb at the top of the modal so you can jump back to any earlier level • runs the starting view shows every sync run for this integration, newest first, with status, sync type (full, update, background), duration, total entities processed, and any error count • steps click into a run to see the individual steps it ran for example, contacts , companies , and deals for hubspot each row shows how many entities were processed, skipped, failed, and whether the step hit a rate limit • step instances steps with paginated api calls expand into the individual pages, with the api method, url, retry count, and rate limit headroom for each page • entities the actual records synced in the selected step each row shows the external id (hubspot id, chargebee subscription id, etc ), the matching custify id, the sync action (create, update, skip, delete), and the skip reason or error message when applicable • api calls the lowest level shows the exact api calls custify made for the selected entity, with method, url, http status, response time, and the request parameters used searching across runs the search bar in the top right of the viewer is context aware it searches within the level you're currently on from the runs view, searching for an external id returns the runs that touched that record from inside a run, the same search narrows to the steps and entities where the record appears this is the fastest way to answer questions like why didn't this contact sync last night? without having to scan run by run custify tip logs are kept for 30 days after day 7 they are automatically compressed in storage, but they remain searchable and viewable in the modal exactly the same way the compression is transparent to you