Hi SAC Experts,
Some of our data actions fail sporadically, while on other moments, they run successful (with same scope & parameters).
Sometimes they fail at the final 'Publish' step, sometimes they already fail at the 'Preparing to execute' step.
2 typical error messages we see in Data Action Monitor are:
The data action "DATA_ACTION_NAME" couldn't run successfully on version "VERSION_NAME" because you don't have the resources available. Try restricting the scope or try again later.
or also:
The results of the data action "DATA_ACTION_NAME" could not be published on version "VERSION_NAME" . You don't have the resources available to publish this version. Please try again later.
1. Is there any way we can see easily which resources were used that essentially blocks our data actions from running successfully? We don't immediately see other actions, reports, etc. in the performance log & statistics stories.
2. We could accept during heavy/peak moments that data actions might run slower... but wouldn't want them to fail. Are data actions not designed to check during 'Preparing to execute' state if they have enough resources, and if not, just re-try a bit later?
How can we ensure better reliability? (except for the obvious refactoring of heavy data-action steps to best of ability)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.