Batch Job - First error: Future method cannot be called from a future or batch method

Today while working on one of requirement, where we need to schedule a job after every fixed interval of time. During unit testing we found our job stuck. Initially we thought, it may be because of non-availability of resources, since scheduled jobs get queued if resources are not available and runs as soon as resource is free. After waiting for 30 mins, we went to Setup >> Jobs >> Apex Jobs to see what is status of Batch Apex. We found that 'Scheduled Apex' i.e. scheduler was in 'Queued', while the 'Batch Apex' i.e. batch was in 'Failed' status. It was causing job to stay stuck.

First error: Future method cannot be called from a future or batch method

We need to be careful against such scenario. We may think that our job is running properly, whereas it may be in stuck status because of exception. We need to do follow to avoid such issue:-

1. Properly unit test job, with all possible use case and mass data. Don't test only for 1 batch, make sure to test it with multiple job.
2. Even after all test, make sure you check health of your job on production environment regulary. Otherwise if error, potentially it may already having impact on your desired business objective.

Comments

Mashup Integration in Salesforce

During preparation for TA certification exam, I came across a word Mashup for integration a number of times. I explored about it and below is description:- Mashups, sometimes called “composites,” are hybrid applications created by bringing together several data sources and Web services to create a new application or to add value to an existing application. Behind the scenes, mashups may require different levels of integration, depending on whether the mashed-up data is only meant to be viewed, whether it can be edited, and whether data is actually transferred between systems. There are three types of mashup:- Client Presentation Mashup - In this type of mashup the integration takes place strictly at the visual level. It makes possible to view data from two or more applications in a browser, without actually moving data between the applications. Example - Google Maps. Client Service Mashup - As mashups evolve, they are becoming more complex and sophisticated. Client ser

Grant Access Using Hierarchies

Problem There is a custom object say 'XYZ' and OWD for this is set to ' Private ', which means record of this can be seen by only owner and users above in role-hierarchy and territory. However, to share this with other user, we can manually share it. The problem is that I don't want other users, who are above in role-hierarchy and territory of the user with whom record has shared, can see it. Solution We can un-check ' Grant Access Using Hierarchies ' check box for object 'XYZ' on 'Sharing Settings' page. We can go to Setup >> Security Controls >> Sharing Settings and click on ' Edit ' button. On the edit page, we can un-check ' Grant Access Using Hierarchies ' for required object. Major uses of 'Grant Access Using Hierarchies' are:- If you disable the Grant Access Using Hierarchies option, sharing with a role or territory and subordinates only shares with the users directly asso

ReadOnly Annotation

Use Case:- You want to show up to 10000 record on single VF page. Count of records based upon some business requirement where number of records could go up to 1 million. So far, it was not possible to achieve above in VF page because of following limitations:- The maximum number of items in a collection that can be iterated over using components such as <apex:dataTable> , <apex:dataList> , and <apex:repeat> is 1000. Normally, queries for a single Visualforce page request may not retrieve more than 50,000 rows. Solution:- But with API version 23.0 , salesforce has introduced ' ReadOnly ' annotation which has following functionality/restriction:- The @ReadOnly annotation allows you to perform unrestricted queries against the Force.comdatabase. All other limits still apply. It's important to note that this annotation, while removing the limit of the number of returned rows for a request, blocks you from performing the following operations

SFDC Know How

Search This Blog