Skip to main content

"Google Chronicle version 42" having issue in "Google Chronicle Sync Job"

  • October 7, 2024
  • 8 replies
  • 78 views
S
Forum|alt.badge.img+10

Hello All,

Has anyone recently upgraded their Google Chronicle Integration to the latest version 42?

I've tested it in a pre-production environment before rolling it out to production and encountered the following error:

"/opt/siemplify/siemplify_server/bin/Scripting/PythonSDK/IntegrationsVirtualEnvironment/#/GoogleChronicle__xxxxxx-84f8-459f-xxxxxxxxxxx_V42.0/tztpdglt.z1o/utils.py", line 939, in fetch_timestamp_for_job
raise Exception("Failed reading timestamps from db, ERROR: {0}".format(e))
Exception: Failed reading timestamps from db, ERROR: 400 Client Error: Bad Request for url: http://server:80/api/external/v1/sdk/GetContextProperty: b'{"errors":{"identifier":["\\'Identifier\\' must not be empty."]},"title":"One or more validation errors occurred.","status":400}'

Has anyone else come across this issue or found a solution? 

8 replies

kentphelps
Staff
Forum|alt.badge.img+12
  • kentphelps
  • Staff
  • October 8, 2024

@skadav Please continue efforts to resolve this issue via your support case.

    f3rz
    Staff
    Forum|alt.badge.img+10
    • f3rz
    • Staff
    • October 8, 2024

    Jobs do not support auto-upgrade or connector-like upgrades via button, so each integration update must be recreated with a code change related to the job. Therefore, I recommend you try re-creating the job first. And if that doesn't help, contact Support for further troubleshooting. 

    S
    Forum|alt.badge.img+10
    • skadavSilver 2
    • Author
    • Silver 2
    • October 9, 2024

    Jobs do not support auto-upgrade or connector-like upgrades via button, so each integration update must be recreated with a code change related to the job. Therefore, I recommend you try re-creating the job first. And if that doesn't help, contact Support for further troubleshooting. 


    Hello,

    How to recreate job in Stagging environment. 

    Thanks,
    Suraj Kadav

    f3rz
    Staff
    Forum|alt.badge.img+10
    • f3rz
    • Staff
    • October 9, 2024

    Hello,

    How to recreate job in Stagging environment. 

    Thanks,
    Suraj Kadav


    1. Make sure that Integration is updated to the latest version in Marketplace
    2. Open Response -> Jobs Scheduler menu -> Job that needs to be re-created
    3. Note config that should remain to someplace such as notepad (+ if credentials are needed prepare them somewhere)
    4. Delete Job instance
    5. Once Job instance deleted, create new one using noted configuration

    This way new instance will use latest code. 

    S
    Forum|alt.badge.img+10
    • skadavSilver 2
    • Author
    • Silver 2
    • October 24, 2024

    1. Make sure that Integration is updated to the latest version in Marketplace
    2. Open Response -> Jobs Scheduler menu -> Job that needs to be re-created
    3. Note config that should remain to someplace such as notepad (+ if credentials are needed prepare them somewhere)
    4. Delete Job instance
    5. Once Job instance deleted, create new one using noted configuration

    This way new instance will use latest code. 


    Thank you but I am aware that this will work in Production Environment. But in stagging there is no option to create new job. 

    f3rz
    Staff
    Forum|alt.badge.img+10
    • f3rz
    • Staff
    • October 24, 2024

    Thank you but I am aware that this will work in Production Environment. But in stagging there is no option to create new job. 


    Could you please elaborate more on what you mean by there is no option to create new job? Job creation should be available in all SOAR and SecOps instances. 

    S
    Forum|alt.badge.img+10
    • skadavSilver 2
    • Author
    • Silver 2
    • October 24, 2024

    Could you please elaborate more on what you mean by there is no option to create new job? Job creation should be available in all SOAR and SecOps instances. 


    Yes, it is possible to create a new job in the SOAR and SecOps instance, but that option is only available in the Production IDE.

    I ensure that all upgrades are tested in the Staging environment before deploying them to Production. However, in the Staging environment, we do not have the ability to add or remove jobs.

    f3rz
    Staff
    Forum|alt.badge.img+10
    • f3rz
    • Staff
    • October 24, 2024

    Yes, it is possible to create a new job in the SOAR and SecOps instance, but that option is only available in the Production IDE.

    I ensure that all upgrades are tested in the Staging environment before deploying them to Production. However, in the Staging environment, we do not have the ability to add or remove jobs.


    @skadav , I'm sorry for the misunderstanding. You mentioned the Staging and Production modes of IDE. 

    Unfortunately, testing jobs there are not fully supported (some of them may work in IDE, some of them won't). I would recommend you to submit an FR to change this so testing all jobs from IDE will be 100% supported. 

    But overall, once integration (especially Chronicle integration) is upgraded, it is highly recommended to re-create jobs in order to upgrade them. 

      Terms & ConditionsCookie settingsAccessibility statement
      Privacy Policy Terms of Service Gen AI Policy Community Guidelines Cookie Settings

      © 2025 Google. All rights reserved.