Super Admin not able to create Company Workflows in the Automator

Forum|Forum|1 year ago
January 31, 2025
4 replies
226 views

I am a super Admin but am unable to create Company Workflows in the Automator

Best answer by ByrneReese

@Technicians Our engineers believe they traced the problem to a caching issue. They flushed the cache. Try again, and let me know if that fixed the problem. If so, we can better implement a complete fix.

Thank you for bringing this to our attention!

Update: we are working to improve our caching mechanism to minimize the chances of this happening in the future.

To help you diagnose this in the future: if you are searching for something in Workflow Builder and can’t find it, then ask yourself when the item you are looking for was created. If it was created in the last hour or so, it is possible the cache is out of date. The cache refreshes automatically in time, so if you are patient the item should appear. If it doesn’t, please reach out, further investigation would be needed.

ByrneReese

Product Manager

@Technicians Do I understand correctly that you do not see the “Company Workflows” tab in Workflow Builder as shown here:

https://ringcentral.github.io/ringcentral-automator-docs/admin/non-users/

This is highly unusual if you are a Super Admin and cannot. Can you share a screenshot of your user in our Admin Portal that shows the role currently assigned to you? Just want to verify.

You might also check what happens when you click “Create Workflow.” Super Admins have the option to select first which extension they are creating the workflow as seen here: https://ringcentral.github.io/ringcentral-automator-docs/admin/manage/#adding-a-workflow

T

Technicians

Author

The First Step

Hi @ByrneReese

Please see attached screenshot. This is from the Super Admin Group

When creating workflows, we are only able to create workflows for extensions or queues that the extension is directly attached to - it is the SMS Fax Recipient for the Auto-Receptionist so only numbers attached to that can be modified.

We attempted to create the rule we want, using the number we want the rule to apply to, and it did not work, until we attached that number to the auto-receptionist.

Thank you

ByrneReeseAnswer

Product Manager

@Technicians Our engineers believe they traced the problem to a caching issue. They flushed the cache. Try again, and let me know if that fixed the problem. If so, we can better implement a complete fix.

Thank you for bringing this to our attention!

Update: we are working to improve our caching mechanism to minimize the chances of this happening in the future.

To help you diagnose this in the future: if you are searching for something in Workflow Builder and can’t find it, then ask yourself when the item you are looking for was created. If it was created in the last hour or so, it is possible the cache is out of date. The cache refreshes automatically in time, so if you are patient the item should appear. If it doesn’t, please reach out, further investigation would be needed.

T

Technicians

Author

The First Step

Hey @ByrneReese,

Yes, it does seem to be working now. Thank you for the fix, and for your time yesterday!

Sign up

Login with SSO

Login to the community

Login with SSO