A temporary error and unauthorized access require different actions. The logs help to recognize the attempt, the message received and any automatic reprogramming.
Read the publishing logs
- Open Log and identify the time interval of the operation to be reconstructed.
- Read level, channel, event and message, comparing them with the relevant content.
- Filter the level when you want to focus on errors and keep the reference to the correct attempt.
- Use the content detail to complete the reading with attempts, external identifier and last error.
Temporary errors and automatic retries
- Open the offending content and read the message before repeating the operation.
- For temporary limits and unavailable service responses, the system can schedule new attempts after two, ten, thirty and one hundred and twenty minutes.
- For credentials, format or permissions errors, fix the indicated cause instead of waiting for an automatic solution.
- Consult the log and number of attempts, avoiding repeated manual submissions while a new attempt is expected.
Putting this into practice
When a post remains in error, open the detail before sending again. Check if the system is waiting for a retry or if the content, credentials or configuration needs to be corrected.
Learn more about Social Publisher.
Comments and questions
Do you have a question about this topic? Open the discussion with a comment.