Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An error has occurred in the following section: [Exception, DisjunctionsNotSupportedException] #301

Closed
kbell2uw opened this issue Sep 17, 2024 · 3 comments
Assignees

Comments

@kbell2uw
Copy link

Time Warp version
1.14

Describe the bug
I receive the following error when clicking Manage Records on the Timeline Configuration Custom Metadata Type:
An error has occurred in the following section: [Exception, DisjunctionsNotSupportedException]

To reproduce

  1. Go to Setup - Custom Metadata Types - Click Manage Records next to Timeline Configuration.
  2. Click Create New View.
  3. Give it a View Name and View Unique Name, and Filter by Field: Label, Operator: Contains, Value: Task, Event.
  4. Go back to Setup - Custom Metadata Types - Click Manage Records next to Timeline Configuration.
  5. See error - you are now prevented from managing configuration records.

Expected behavior
No error when loading the timeline configuration metadata type.

Desktop (please complete the following information):

  • OS: Windows
  • Browser: Edge

Additional context
I started getting this error after trying to create a new view of timeline configuration records related to tasks and events. After I saved that view, I started getting this error every time I try to access Manage Records for Timeline Configuration.

Copy link

Hello @kbell2uw , thank you for submitting an issue we appreciate your time. We will take a look and give you an update as soon as we can. We aim for a 72 hour response time.

@deejay-hub
Copy link
Owner

Hi @kbell2uw I believe this is a Salesforce issue. Does the following article help you
https://help.salesforce.com/s/articleView?id=000384700&type=1

@deejay-hub deejay-hub self-assigned this Sep 17, 2024
@deejay-hub deejay-hub added the triage Investigate and triage issue label Sep 17, 2024
@kbell2uw
Copy link
Author

Ah, thanks so much! Appreciate the quick find - that resolved the issue!

@deejay-hub deejay-hub removed the triage Investigate and triage issue label Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants