Error in creating Queue Trigger when migrating from Classic to Modern folders

[Foreverlearning]

After migrating from the Classic folder to the Modern folder using the migration tool provided in the Cloud Orchestration. I realized that all the queue triggers were gone:

When I tried to create the same queue trigger, an error message was shown:

This option is currently not available because it’s already associated with a process in another folder. Please add a new queue with the same properties in this folder.

I have double-checked all the triggers in all the folders, but there is no such queue trigger:

[ptrobot]

Have you checked the other folders?

[Foreverlearning]

Yes, I have checked in all the available folders in the modern folder, including the one in the classic folder. There is totally no queue trigger found in any of the folders.
As shown in the screenshots below. There is totally no queue trigger

[Anil_G (Anil Gorthi)]

@Foreverlearning

If its possible try to delete the wueue and recreate …and check if the issue is resolved

Alternately try using orchestrator api to check if any triggers are present and delete them using api

Cheers

[ptrobot]

Ok, that’s strange. If you check it via the Queues tab, how does it look?

[Foreverlearning]

The queue items are important to me as i have to keep track of the past transacted items and also for audit purpose.

26 items in Orchestrator

API returns 26 items too.

[Foreverlearning]

There is no associated queue

[Anil_G (Anil Gorthi)]

@Foreverlearning

I want you to check if there are any triggers using api…if it returns any then you have option to delete also from api …ao if not shown on ui atleast from api you can get it

Cheers

[Foreverlearning]

Thanks for the explanation. I have checked that all the values returned from the ProcessSchedules via API call are for time trigger. There is no queue trigger at all.