This article will cover some possibilities as to why your Workflow may not have triggered when expected.
Triggers Syncing into BetterCloud
It is possible that your Workflow has not kicked off due to the triggering event not yet syncing into BetterCloud. You can confirm that the change has synced in by clicking into the targeted entity from the Directory or Files grid. To check on the scheduled sync times across our different Connectors, please refer to this article.
If your Workflow is triggered by an Alert, it is also best to first confirm that the results have populated in the Triggered Alerts section. Please note: the Workflow will only run for targets that exceed the Alert threshold from the point of publishing the Workflow going forward.
If you need to re-trigger a Workflow, please be sure to confirm that the first change has synced into our system before making the second change. For example, if you are triggering a Workflow with an OU change, please wait until the move out of the OU is shown in the User 360 fly-out for the user, as so:
After the change appears in the User 360 fly-out, you can then make the change back into the OU that meets the Workflow condition to re-trigger it.
Sometimes the system could be processing a high volume of data which could cause some delay in Workflows triggering. Although the data has not been brought in at the expected time, it is in a queue and will work through the system, allowing the Workflow to trigger. If you find that data is taking a long time to update in BetterCloud please contact support by utilizing the in-app chat on the bottom right corner of the page or emailing firstname.lastname@example.org.
Workflow or Alert Conditions Not Met
It is also possible that the triggering change has not met the conditions set up in the Workflow. For example, if your Workflow has multiple conditions, as so:
It could be possible that the entity being pushed through the system may meet one, but not all, of the conditions and therefore will not trigger the Workflow. This can be resolved by re-triggering the Workflow as described above with a change that matches all of the conditions.
If your Workflow is triggered from an Alert, you can also confirm that the triggering event meets the Alert conditions under Alerts > Manage and clicking the “Edit” button next to the Alert.
Okta to G Suite Provisioning
If you are provisioning a user from Okta to G Suite, it is possible that the user is missing the “primary” attribute that is necessary to trigger a Workflow. BetterCloud requires this attribute to exist for the user in order to properly ingest user data and run Workflows. You can learn more about this scenario and learn how to add the necessary attribute in this article: https://support.bettercloud.com/hc/en-us/articles/115003482613-Okta-to-G-Suite-Provisioning
"In Progress" Workflows
It is also possible that your workflow is actively running, but you don't see it in the Workflow Results. If a Workflow is in progress or has a Wait for Duration action in it, it will be on the last page of your results when you select "View Results" from the Workflow Manager. Here is an example of a workflow with a Wait for Duration Action:
If all signs point to your Workflow kicking off, and you are working with a long workflow or one with a Wait for Duration action, it's a good place to check!
If you run through this article and still do not see your Workflow trigger, or are experiencing any other issues, please check our status page or reach out to Support either through in-app chat or emailing email@example.com.