Uploaded image for project: 'AdMax'
  1. AdMax
  2. ADMAX-2252

Google Account Sync: manual intervention required

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: unspecified
    • Component/s: Google
    • Labels:
      None
    • Environment:

      Operating System: Linux

      Platform: PC

    • Bugzilla Id:
      3202

      Description

      Unfortunately there were some errors that happened after the staging tables had

      been loaded with the newest data. This means that future syncs won't detect the

      differences the last one detected, so some campaigns could go without

      synchronization.

      To fix this, we need to use a transaction when doing difference checking, table

      replication, loading the sync_google tables, and bid difference checking. We

      need to ensure that the same connection is being used for all operations. Once

      ALL steps have completed successfully, then we can commit the transaction before

      the SearchEngineUpdater syncListings/getListings methods are called so those

      methods can read from the tables with the new data.

      Other Enhancements:

      1) We need to add support for a --force-sync flag, which skips the difference

      checking and loads the sync_google tables and runs a sync for everything.

      2) We need to re-implement the --seaccount|-A flag. This flag would imply the

      --force-sync flag, and ONLY pull a report for the CSV list of campaigns, skip

      difference checking, and ONLY clear and load the staging table with that list of

      campaigns (add the "campaignid in (...)" clause to the delete statement that

      clears sync_google tables).

      Account-specific issues requiring manual intervention:

      There is currently a workaround to set the searchEngineAccounts.lastChecked

      column to null, to force a synchronization. We'll need to do this for the SE

      Account IDs listed below.

      There are some accounts that need to be manually fixed:

      TSA Account 92 google sync tables were loaded but there was error after.

      SE Account IDs: "36124","2233","13449","4151","32284","1262"

      JOBID 3736656 (stderrCompressed-3.txt)

      There appears to be an issue with SEUserID 1391. 3 accounts are affected:

      TSA Accounts: 454, 453, 447

      SE User ID: 1391,1389

      Also, some SE Account IDs are affected

      SE Account IDs: "29754","31825","27074","31826","31824"

      JOBID 3735638 (stderrCompressed-4.txt)

      JOBID 3735639 (stderrCompressed-5.txt)

      JOBID 3735640 (stderrCompressed-6.txt)

        Attachments

          Activity

            People

            • Assignee:
              patrick Patrick Crane (Inactive)
              Reporter:
              therouxj Jeff Theroux
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: