Hi @jrichards ,
I can’t reproduce the problem of the timeout, but we are having the following problem. I will try to explain it as precisely as I can:
After we make the API call to obtain the mappings ( [rest/atlassian-connect/1/migration/mapping) , in this case, we obtain the workflowRules (“jira/classic:workflowRule”)
The next step would be the one that is giving us problem. For each workflowRule, we make the api call to obtain the transition rule configurations (/rest/atlassian-connect/1/migration/workflow/rule/search).
We obtain results, but not like before. Previous week, on Friday, from all the mappings obtained, there were some values amongs them which contains in the array validRules the rules related to our application post-functions/conditions/validators. This would be an example of a valid answer we obtained before:
Client 6bdcf155-3a1c-3bb5-9599-69880670cc06, migrating workflow rule:
{
validRules: [
{
workflowId: { name: 'DEMO: Project Management Workflow (1)', draft: false },
postFunctions: [
{
id: '9e98bad4-a828-43a9-8b91-f23cfdbfb490',
key: 'addComment',
configuration: {
value: '{"WORKFLOW_RULE_CONFIGURATION_SERVER"}',
disabled: false
},
transition: { id: 11, name: 'Start Progress' }
}
],
conditions: [],
validators: []
}
],
invalidRules: [],
workflowEntityId: '3c60382b-d2fd-4544-a411-44972df27605'
}
As you can see, in that call we obtained correctly the values related to the validRules of our application.
Besides that, we also obtained some transition Rules with invalidRules, like the following one:
{
validRules: [],
invalidRules: [ 'ccbc6126-434c-4573-aa8f-34a1688785ae' ],
workflowEntityId: '1d99175b-3e77-4ca1-a6ad-a19da14a5b08'
}
We are only obtaining transition rule configurations where the validRules array is empty, that is our problem. Now, we only obtain transition rule configurations with invalidRules, instead of transition rule configurations with validRules and invalidRules
Regarding your questions:
1. The domain name of the cloud site you’re using
2. The full, specific error message that’s returned from the endpoint
In this case, the error is that we are not obtaining any value in the validRules array anymore, it’s always empty. All the transition rule configuration obtained ae values with invalidRules.
We are not obtaining any json like the one I wrote or the one that appears in the official documentation:
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-app-migration/#api-rest-atlassian-connect-1-migration-workflow-rule-search-post
3. The time (and timezone) that you have made a request
I just did another migration between 09:34 AM and 09:47 AM (Madrid Timezone, GMT+1) today (16th December)
Regarding the timeout error, we’ve not been able to reproduce it, but it happened Monday 13th December, between 10:00-14:00 PM GMT+1, I took this screenshot:
If you need any other information, please let us know.