#Appexchage Apps57 discussing

Hi @Grishwanth Yerramekala - Looking at your screenshot — the report is stuck loading and throwing the retrieval error on the Object Permissions tab for Case. This is almost always a token issue at the user level, not a permissions gap.

Three things to try in order:

Go to personal settings, find Authentication Settings for External Systems, delete the UAPA entry and re-authenticate from scratch. This is the fix for most of cases like this.

If that doesn't work, check your Named Credential, make sure it's set to Per User principal type, not Named Principal. If it's Named Principal it won't pick up your user-level auth at all.

Finally verify your connected app has api and refresh_token in the OAuth scopes. Missing scopes cause this exact generic error rather than a clear OAuth message.

If all three check out and it still fails, pull a debug log while running the report, the outbound callout response will have a more specific error than what the UI shows.

Hi @Vikas Kumar Lal Das, 

Maybe you are a bit confused what is Hyperforce. Simply it's Salesforce migrating instances from own managed data centers to 3rd party data centers (AWS Cloud infrastructure). So if you have an Production org migrated to Hyperforce, now you can request Salesforce to move it from one instance to another based on location (here you can find them https://help.salesforce.com/s/articleView?id=000396845&type=1). If you have two orgs migrated to Hyperforce, both can be located on different data centers. But you can't have one org stored in two different instances at the same time.

Hope this answers your question

Br,

Artūras

Thank you, that was useful. I had expected it to be in a single place and maybe further along, but as you say its all still quite new and evolving. 

I will reach out to the Salesforce Partner Community to get on the wait list.  

Thanks 

the error isn't about the user's password, but rather an Apex Trigger

failing behind the scenes when Salesforce tries to update a user record during the login process.  

When a user logs in, Salesforce often updates last login date on user record. If you have a DLRS rollup on the User object, and that rollup tries to update a parent record that has a Validation Rule or a Missing Required Field, the login will crash. 

As a solution, temporarily deactivate any validation rules to see if the user can log in. If they can, you need to adjust your validation rule to exclude the DLRS background user or handle the missing data. 

If this is a brand new user, they likely don't have the permissions required to trigger the DLRS code. Assign the DLRS Standard User (or similar) permission set to the new user. Even if they aren't "using" the tool, if they perform an action that triggers a rollup, they need Apex access to the DLRS classes. 

Hope this helps. Feel free to mark this as helpful for others :)

This something unexpected but we can try to locate “User Adoption” via Metadata (not UI)

1. First Check in Reports with anything names "User Adoption" 

2. Also Check in Dashboards named like this or having having report types named "User Adoption"  

If found → delete it 

Yes. These are supported. 

Documentation is on the AppExchange listing (

) under the more details tab. There you'll find a Config Guide and FAQ Guide. Open in an incognito window if you have issues opening. 

These guides show you how Time Warp knows which objects to plot and the metadata comes with support for Notes and Files (via ContentDocument) support for many standard objects (you just have to activate the record) or you can create your own records for custom objects using the existing records as a guide of how it's done. 

Any questions you can ask here

Hello @Anna Umansky, "Recently Viewed" list view is empty if you have never clicked to see a record detail page of the same kind. Please select another list view to access your data (dropdown next to the list view name) and check your list view filters (funnel icon). 

Have also a look on custom Apex logs / Debug logs / Batch errorsn according to the elements coming with the package. That may give you hints on what may happen behind the curtains. You may also have a technical log object coming with the package (to check against the documentation, appExchange package team). 

Eric