We have a couple of DW 9 sites hosted in Azure with various integration jobs.
Each job is trigged by an external integration process. The problem is that the token generated by DW that is appended to the url changes, making it unable to trigger integration jobs from the external process without updating the url. When trying to trigger an integration job with the wrong token I get the following message: "Token missing, activities canceled".
Why does the token change?
Is there anything I can do to prevent this, to ensure that the integration job can be triggered wihout needing to modify the url to call?
Here's an example of where the token has changed:
Url generated by url builder: https://xx/admin/public/webservices/integrationv2/JobRunner.aspx?jobsToRun=R5K+-+VariantOptions+-+Color+import&token=33f790895f88adf5b7e814ee4b5b6130
Url generated by url builder a couple of days later (same integration job on the same DW installation):
https://xx/admin/public/webservices/integrationv2/JobRunner.aspx?jobsToRun=R5K+-+VariantOptions+-+Color+import&token=a2bb40d46464947986b512684764e8b0
