Space updating

It appears at least one of my spaces stopped updating on 9 January.

It was reported to me that one of the analytics reports stopped updating. I look at the space and I don't see how to force an update of the data into the space.

I took the 'Birst for Administrators' course and I have reviewed all of my notes and data. I cannot find anywhere we went over this subject.

TIA

Inquiry Tab Placement.docx

Find more posts tagged with

Birst - General Discussions

Comments

Diane McElhiney

The answer to your post can take many different avenues for research. First, the log for the Birst Agent needs to be reviewed for the space(s) where the updating stopped. You can verify the spaces by displaying the history of the Orchestration controlling extract or publish into the space. In the Orchestration if the failure is at an extract step, in Monitoring, expand the section named for the Agent connection, hit details and then download logs. If the failure is at a publish step in Monitory, expand the section named Publish in the corresponding space and download that log. Reviewing the logs search for error or except keyword (please note WARN message need to be reviewed for severity). Is there something causing data not to load.

To 'force' an update, again can take different course of actions depending on your environment. Are you a Cloudsuite Birst Analytics Solutions customer as there are specific steps for these implementations? If these are your own modeled space, then you'll have to determine how incremental refresh start dates are tracked within your environment.

With all the above being stated, I like to have an off-line conversation with you. I'll message you.

0712131256598360.doc

Diane McElhiney

In case there are other users which view this posting, it was discovered by reviewing the Orchestration history and the error shown stated the Orchestration could not execute as the Owner (creator of the Orchestration) was an Inactive user within User Management.

The solution is to copy the Orchestration, then rename the current Orchestration (i.e. prefix with z), then rename the copy to remove the Copy of prefix.

One further best practice, ideally we like to see Orchestrations associated with a generic id so as not have to worry about attrition in staff therefore failing into the same trap. A generic id can be created, associate a team group email perhaps and associate a password.

Please beware notifications are not received regarding the Orchestration execution status as it is sent to the creator. Other users can be assigned as additional emails under the action menu of the Orchestration.

Copyright © 2025 Infor. All rights reserved.