It seems like back ups in Configuration Hub are limited to 100 workflows. I imagine sp-config also has a similar limitation. Other objects don’t seem to have this 100 limit. Any chance that can get increased? If not, what’s the strategy for a customer to implement a true backup versus a partial backup?
Hello @SteinerBBQ ,
100 workflows looks like a lot (unless they’re not all active), but I believe it is a soft limit that could be increased by openning a sailpoint support ticket.
It seems to me like the limit of roles at 30k roles, the limit of active workflows at 60, or the max of workflows’ executions at 400k/day.
Nothing is mentionned in the configuration hub documentation
BR
1 Like
Hi @SteinerBBQ
Did you ever get an answer to this? My understanding is there is a limit to the total number of workflows in a tenant, but I don’t believe this is published. You may have to talk to your account executive.
Hey
I don’t think this is a “tenant workflow max” limit. It looks more like a Config Hub / export job limit for the WORKFLOW object type.
What I’d do:
-
Don’t rely on Config Hub as a full backup. It only backs up supported config objects (and it doesn’t include secrets).
-
Back up workflows using SP-Config export in batches.
Instead of trying to export all workflows at once, split them (by names) and run multiple exports until you have them all. -
If you want long retention, sync backups to S3 (Config Hub supports that) so you’re not limited by what’s stored in the tenant.
-
If you really need “all workflows in one shot,” open a Support case and ask them to confirm/raise the WORKFLOW export limit (since there are documented object limits that Support can override).
SailPoint Customer Agreements Definitions and Additional Terms - SailPoint Product Documentation that has the breakdown for acceptable use limits. One of the best pages that often gets overlooked in my opinion. The max for active is 200.
1 Like
Thanks that’s helpful!
Did any of the options @amrdodani presented work for you?
Thanks for sharing that link — it’s super useful. It clarifies the acceptable-use limits for active workflows (100/200 depending on suite/contract).
But the original issue here is slightly different: Config Hub backups are only capturing ~100 workflows. The Config Hub backup docs say selecting WORKFLOW should include all objects of that type (unless filtered) and backups can include up to 5,000 objects (Support can override).
So this still looks like either (a) Config Hub only exports active workflows, or (b) there’s an undocumented export cap for WORKFLOW. For now, best workaround is exporting workflows in batches by name via Config Hub / SP-Config export, and opening a Support ticket to confirm/raise the WORKFLOW export limit
Yes, workarounds are pretty straightforward. What I’m more interested in from someone at SP is to ensure ppl don’t assume Config Hub takes a true backup only to find out it doesn’t. It’d be helpful for the documentation to be present. I’ll have someone on my team raise a support ticket in early Jan.
@vkashat Yep — the workaround works, but it’s still a gap in Config Hub expectations.
For us, the only reliable way has been exporting WORKFLOW in batches (use Objects by Name and run multiple backups/exports). Config Hub also supports sending artifacts to S3 for retention.
I don’t think the “100” you’re seeing is the same as the active workflow acceptable-use limit (that contract table is about active workflows, not backup/export).
What’s still unclear (and what Support should confirm) is whether Config Hub backups are currently only exporting active workflows or if there’s an undocumented per-type export cap for WORKFLOW — because the Config Hub docs say selecting an object type should include all objects of that type (unless filtered) and backups can go up to 5,000 objects with Support override.
+1 to Philip’s point: this should be explicitly documented so nobody assumes Config Hub is a “full backup” for workflows.