Split synchronizer doesn't get changes

Comments

5 comments

  • Bilal Al-Shahwany

    Hi Pedro, Are the API Keys both belong to the same environment? Changes in Split definition usually happen in one environment and the API Key has to be associated with that environment in order to capture the change.

    Thanks

    Bilal

    0
    Comment actions Permalink
  • Pedro Rodrigues

    Hi Bilal. Thanks for the reply.

    Yes, both API keys belong to the same environment, I even double confirmed it. That's why I found this behaviour strange.

    0
    Comment actions Permalink
  • Bilal Al-Shahwany

    Hi Pedro, thanks for the info, I have seen this issue reported recently, the root cause is the cdn is not fetching the latest info, rather return the old caching.

    We are working on releasing a workaround fix for the synchronizer, please watch for the next synchronizer build.

    Thanks

    Bilal

    0
    Comment actions Permalink
  • Pedro Rodrigues

    That's great, thanks for the info.

    0
    Comment actions Permalink
  • Pedro Rodrigues

    Hi again!

    Can we expect v4.0.3 to include a fix for this?
    I see that the docker image is currently in v4.0.3-rc2, it seems to work. When is the expected release?

    0
    Comment actions Permalink

Please sign in to leave a comment.