AnsweredAssumed Answered

What happens to a task/process if the user alloted credits are reached?

Question asked by rastrauch Champion on May 4, 2017
Latest reply on May 25, 2017 by vscott1

During our last annual credit period, about half of our credits (~2300) were used up by a rogue/test process.  The users thought they had stopped the process, but it either continued processing (loading??) or it had already used the credits.  In this case it wasn’t critical, since we didn’t run out of credits, but with the new credit period just starting we are hoping to prevent this. [btw - since we are all learning are way around still, it could happen to any of us]

 

To help, I just activated the Configure credits—ArcGIS Online Help | ArcGIS for our enterprise account and have allotted a small amount of credits per user. (10-25 pre user)

 

But the question was asked, “What happens when a user hits their limit during a task/process?” …and I would add, “rogue/test  or legitimate?”

 

She was able to find “If members exceed their allocated credits”  on the same page as the link above which states.. (emphasis added)

Some members may use ArcGIS credit-consuming functionality extensively and, in the process, exceed their initial credit allocation. If this happens, designated administrators will receive an email notification that the member has exceeded their allocation. The member will also receive a notification advising them that one or more administrators have been notified that their ability to perform batch geocoding, network analysis, spatial analysis, geoenrichment, demographics, elevation analysis, and tile generation will be suspended until their administrator updates their allocation. As a designated administrator you can either set their allocation to no allocated limit or provide them with additional credits using the same tools you used to make the original allocations. Alternatively, you can contact them directly to confirm that no additional credits will be allocated to them

This is a little vague to us regarding:

  1. What is the meaning of “suspended” in this situation?
  2. Does it pause or cancel?  Do we have an option to choose, i.e. if it hits the limit because of a rogue/mistake, can we cancel it?
  3. If more credits are allotted, does it pick up where it was ”suspended”?  Is this automatic, or can we turn it back on?

 

I think what we would hope for is, it the limit is hit and we get the email, that the process would immediately pause, and then allow us to either allocate and continue or cancel. 

 

If a low limit is hit and the task (or storage ??) is paused, it would give us a chance to review whether the storage/process is the best use of the credits or if there is a better alternative. (so much of what we have done thus far has been learning testing, but we are starting to get more real items in place.)

 

I understand the

"Some of your organization’s total number of credits may be consumed through storage, premium content, and app-related activities. You may find it advisable to maintain your budget with these activities in mind."

but, it's more the evening/weekend work, or the testing of something just to find out what it does, that is, the things you can't predict, with the wide distribution of users and needs, that this post is most concern with.

 

Thanks

Outcomes