A common issue we run into is that pushes to Salesforce fail after cloning a database to a dev site, where the site is connected to a different SF instance. This makes all the mapping objects invalid, but the IDs still get included in push attempts. This patch suggests that this could be the issue when certain errors are thrown, and also improves the logging messages.

This could be extended around the module, but the key here is isolating those ID mismatch errors and making them obvious.

Comments

gcb created an issue. See original summary.

gcb’s picture

StatusFileSize
new4.2 KB

Ignore this patch, misclicked the upload.

gcb’s picture

StatusFileSize
new3.68 KB

  • gcb committed 267acd3 on 7.x-3.x
    Issue #2910688 by gcb: Improve errors for debugging purposes
    
gcb’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.