Pipeline Sync Inconsistency

Having an activity logged for a candidate being removed from a pipeline would be beneficial. Currently, when a candidate/contact is removed from a job, no activity is logged on the summary page for that candidate. The job remains on their page, but now it doesn’t have a status for the candidate. For our reporting, it would help to have a removal activity and not leave the job on their page. Currently, the GET Retrieve Activities API returns no new activity record for this action, so there’s no way to keep specific reports in sync for pipeline activities. In our Crelate API integration service, we use this endpoint with verb_ids and modified_after/before params to sync the latest activities related to pipeline moves in a timely manner. This removal operation w/o activity will lead to a pipeline sync inconsistency.