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

First error: Invalid Id for Account #185

Closed
sbaird80 opened this issue Jun 2, 2015 · 11 comments
Closed

First error: Invalid Id for Account #185

sbaird80 opened this issue Jun 2, 2015 · 11 comments
Labels

Comments

@sbaird80
Copy link

sbaird80 commented Jun 2, 2015

A scheduled job throws an error "First error: Invalid Id for Account" I have 9 summaries all scheduled to perform counts sum jobs at a scheduled time each night.

@afawcett
Copy link
Collaborator

afawcett commented Jun 3, 2015

This feels like its related to issue 140 as well.

@afawcett
Copy link
Collaborator

afawcett commented Jun 8, 2015

Can you share the rollup definitions your using please?

I think i have a hunch about whats going on.

It relates to the OwernId being able to point to different parents i think....

@sbaird80
Copy link
Author

image
image
image
image

**Note I have changed them to realtime since posting this issue

@afawcett
Copy link
Collaborator

Are you still getting the issue?

@afawcett
Copy link
Collaborator

Also are any of your Session__c records owned by Groups/Queues rather than Users?

@sbaird80
Copy link
Author

Hi Andrew, not since changing to realtime mode. All session__c records are owned by users only

@afawcett
Copy link
Collaborator

Ah ok, so when in scheduled mode, it was possible that Session__c records where owned by Groups/Queues? If so, i think i've spotted the bug! 👍

@afawcett
Copy link
Collaborator

afawcett commented Jul 4, 2015

Another example here.

@afawcett
Copy link
Collaborator

afawcett commented Jul 4, 2015

Ok i've made a fix in master for this, i'll package it shortly with a few other fixes i want to make.

IMPLEMENTAITON NOTE:

  • This fix will not address the issue for existing Lookup Rollup Summary Schedule Items records that have been incorrectly setup prior to this fix.

@afawcett
Copy link
Collaborator

afawcett commented Jul 5, 2015

Ok, i've made a further fix so that the schedule job will tolerate existing invalid schedule item records without error, it will delete them as well.

@afawcett
Copy link
Collaborator

afawcett commented Jul 6, 2015

Fixed in v1.21 release.

@afawcett afawcett closed this as completed Jul 6, 2015
@afawcett afawcett removed the priority label Jul 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants