We are running on a 5.5 environment and have come across a new error on a scheduled workflow. We have a scheduled workflow that runs every minute, and was running for 30 days before it started failing. The workflow pulls data from a database, runs a separate workflow based on database results, then updates the database with the status of the workflow run. The error we started receiving is "Cannot execute workflow : Bad credentials. SamlToken is not valid." I am able to create a new instance of the schedule for the same workflow, and it works perfectly fine. If I try to resume the original workflow in the scheduler, it will fail.
Has anyone run across this issue or something similar before? Is there any type of timeout set somewhere that will only allow a scheduled workflow to run for 30 days at a time?
Thanks,
Dan